On Sat, 17 Jan 2009 05:56:01 -0800, Mike Porcellana
<MikePorcellana@xxxxxx> wrote:
Quote:
>Greetings all. I'm studying for my MCSE in Server 2003, and am also a
>Technet Plus subscriber. My machine at home is custom-built, and believe
>that it has plenty of horsepower; Intel Core i7 920 CPU, 6 gigs of DDR3-1333
>RAM, an X58 Gigabyte board, a pair of 150GB RaptorX drives, and a 500GB and a
>1.5TB SATA drives. Here's what I'd like to setup.
>
>I want to create 2 virtual machines: one running Server 2003 SP1, and one
>running XP Pro. In and of itself, this isn't a problem; I can do this easily
>under Virtual PC 2007, I'd ASSUME I can do this also under Virtual Server.
Why would you want to do this under Virtual Server 2005? If you do not
intend the test domain to be a 24/7 system but instead be used
interactively by you when studying then I suggest you do this under
VPC2007 since it is a lot simpler and you also already know how to do
it.
If you absolutely need 24/7 operation then create just the server in
VS2005 and keep the workstation XP in VPC2007. A workstation is much
easier to access in VPC2007, than in VS2005.
Quote:
>But, the issue is this: I need to have both these machines "see" and speak
>to each other in the same domain. In the MCSE literature, they're using the
>Microsoft standard contoso.com domain (which is used in all MS Press books).
>I guess my main issue/question is how to configure the networking options
>BOTH in the Virtual PC program, AND once each VM is running, in each
>machine's network properties settings. I don't think it's critical that
>either machine can "see" the outside world (aka the Internet); I feel that
>would be a bonus.
>
>So folks, do any of you have experience at this? Any and all help is
>immensely appreciated!
As above:
- Use VPC2007SP1 as your base
- Create both virtual machines normally, but assign the networking to
"Local only". This will create a private network for the two machines
only so you will isolate them from everything else. A good thing when
you try out stuff. Note that this also precludes using Internet and
accessing the host machine.
- When you start up the guests you will find that they will not yet
communicate because the virtual NIC in both will *not* get a working
IP address since your outside network is isolated.
- So now open the NIC properties in each and set the IP address
manually to something private like 192.168.1.1 for the server and
192.168.1.10 for the XP client.
Now you have a small network with two computers that is isolated from
the rest of the world and can start working on it. Note that from now
on you need to learn from your course how to manage the serber and
domain, so I won't go into that here.
To get Internet connectivity you need to do the following:
- Shut down the server guest completely
- In tye VPC2007 settings for this guest add another NIC and for this
point to the host NIC so that this NIC will be a part of your external
network.
- Start up the server again and check that the server now has Internet
connectivity.
- Next enable the routing role on the server such that it routes from
the internal NIC to the external NIC for any PC on the private
network.
- Then in the XP guest open again the NIC properties and set the TCPIP
gateway to the server's IP (192.168.1.1 in the suggestion above)
I hope this is all steps (taken from memory). Test now that the XP
machine will get Internet connectivity too, this traffic will be
routed by the server guest out to your internal LAN and from there
out to the Internet. Note that the Vista host is not involved in this
at all.
Any other things you need to do on this small network should be
described in your course.
--
Bo Berglund (Sweden)