Title: RE: [ActiveDir] OT: Virtual Server 2005
The answer is that you should have nothing
entered in the default gateway field for the internal (TestLAN) interface. Traffic
is flowing now.
Sorry to waste the bandwidth.
-- nme
From: Noah
Eiger [mailto:[EMAIL PROTECTED
Title: RE: [ActiveDir] OT: Virtual Server 2005
Hi Glenn:
I have been building a configuration similar to what you recommend, but using RRAS (I don't own ISA).
I have RRAS running on the physical host. This has two physical NICs (ipconfig at the end of this post): ProductionLAN and Te
Sent: Tuesday, 30 November 2004 6:15 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT: Virtual Server 2005
Thanks.
>From your descriptions, I think I would want to use NAT only on the NIC
connected to the production network. That is, have all of the traffic from
the virtual network ap
ailto:[EMAIL PROTECTED] On Behalf Of Your Name
Sent: Monday, November 29, 2004 11:15 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT: Virtual Server 2005
Thanks.
>From your descriptions, I think I would want to use NAT only on the NIC
connected to the production network. That is, have al
Thanks.
>From your descriptions, I think I would want to use NAT only on the NIC
connected to the production network. That is, have all of the traffic
from the virtual network appearing as a single address on the
production network.
Since I want everything on the test network (virtual and phy
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004
1:36 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT:
Virtual Server 2005
Noah,
There are a couple of ways to do this, but
essentially the REAL (ie the physical NIC) in the physical server has the
Virtual Server NIC driver
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004
1:36 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT:
Virtual Server 2005
Noah,
There are a couple of ways to do this, but
essentially the REAL (ie the physical NIC) in the physical server has the
Virtual Server NIC driver
le to
allocate enough memory to each VS to speed up performance, but hey, money can
fix that *grin*.
Glenn
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Noah
EigerSent: Saturday, 20 November 2004 5:27 PMTo:
[EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual
Server 2005
Hi Noah,
I prefer the sysprep/copy method; although using the differencing disks option
is attractive.
The oringinal system I'm going to SYSPREP is always mutli-homed. The first NIC
I put into Host Only mode so it talk to other Hosts on my system. The second
NIC I NAT/Bridge to the external
ember
19, 2004 1:21 PMTo:
[EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server
2005
Thanks all. I will play
around with the various methods of duplicating servers (Al, I assume by PXE you
mean in combination with RIS? Do you use a virtual RIS
server?)
As for the networking
portio
them and your all set.
Regards,
Aric
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Noah Eiger
Sent: Friday, November 19, 2004
10:27 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT:
Virtual Server 2005
Ok. Let’s just say that was
scary-easy (i.e
L PROTECTED] On Behalf Of Dean
WellsSent: Saturday, November 20, 2004 4:05 PMTo: Send -
AD mailing listSubject: RE: [ActiveDir] OT: Virtual Server
2005
Did
you try the vmware-mount.exe command yet? Now that, I love! As for
the rest of this release of 5, let's just say it's qui
PROTECTED] On Behalf Of Ulf B.
Simon-WeidnerSent: Saturday, November 20, 2004 5:33 AMTo:
[EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual
Server 2005
You can automate newsid with command line switches as well,
and it changes the computername in the same process as well - fairly easy - I
ng to say if you don't use sysprep.
--Brian
Desmond[EMAIL PROTECTED]Payton on the web!
www.wpcp.org v - 773.534.0034 x135f -
773.534.8101
From: [EMAIL PROTECTED]Sent: Fri
11/19/2004 3:16 PMTo:
[EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual
Server 2005
I do
Ok. Let’s just say that was
scary-easy (i.e., deploying new machines). Thanks! Wow, if only real life could
run in RAM.
Someone asked me to describe generally
what I was looking to do. I want to setup a test environment that contains:
2 DCs
1 Exchange box
1 database server
1+ XP Pr
n the web! www.wpcp.org v - 773.534.0034 x135f - 773.534.8101
From: [EMAIL PROTECTED]Sent: Fri 11/19/2004 3:16 PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005
I don't use sysprep. I just use newsid from sysinternals. Then I edit the
.vmc to reflect the new VS name/loca
PROTECTED]
Subject: RE: [ActiveDir] OT:
Virtual Server 2005
Thanks all. I will play around with the
various methods of duplicating servers (Al, I assume by PXE you mean in combination
with RIS? Do you use a virtual RIS server?)
As for the networking portion, I find that
when I add a virtual host
RIS is just one way of doing it. Any PXE system could
be used I would imagine ;)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Noah
EigerSent: Friday, November 19, 2004 4:21 PMTo:
[EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual
Server 2005
Thanks all. I will
address from my “real” network.
Also, are there issues with running the
host machine on a machine that is joined to a real domain?
From: Mulnick, Al
[mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004
12:38 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT:
Virtual Server
that Today is the Tomorrow you were worried about
Yesterday? -anon
From: [EMAIL PROTECTED] on behalf of Mulnick, Al
Sent: Fri 11/19/2004 12:38 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT: Virtual Server 2005
Networking outside the box is usually done by
Networking outside the box is usually done by adding the
virtual host to the phys host network card. The phys NIC acts as a router
in this case and everything is NAT'd off to the external
network.
That's the same for letting the hosted OS access anything
off the host server whether internet
The newsgroup
is setup. Microsoft.public.virtualserver – it’s on msnews. I post there.
To connect a
virtual network to your LAN, you need to map it to a NIC in your PC. If your
thought process is to do NAT for a whole virtual network, you need to setup a
router server. I just have an im
An “internal” virtual network
can be configured to allow all Virtual hosts to communicate together without
interacting with other physical hosts on the VS2005 servers “real”
network.
VMs can be connected to the real network
of the VS2005 server allowing them to interact with all hosts on t
23 matches
Mail list logo
