Vista - Virtual Environment (AD,DHCP,DNS) - Gettings VPCs to see each othe

I've been reading several of the threads in this newsgroup to try to set up a
virtual network and now I'm stuck because I can't get the virtual PCs (Xp Pro
and Win Serv 2003 R2) to see each other when they are connected local only.

My end goal is to connect the client XP machine to the Server machine in the
virtual local network.

When I created both machines, I originally connected them directly to the
network so I could receive updates. Then I tried installing AD (and DNS) on
the server. Then I started reading the forums, so I decided to set both
machines' network adapters to local.

I then ran the utility in Win Serv 2003 R2 that automatically sets up the
server with AD, DNS, and DHCP. It configured the IP address to be
192.168.0.1 and gave it a DHCP range, but I'm at a loss on what to do on the
XP machine to get it to see the server.

Any ideas?

"Ben Mc" <Ben Mc@xxxxxx> wrote in message
news:2333BD1D-3649-4E39-83E5-5BAC3AE55153@xxxxxxLocal Only is a good option to run a domain. It keeps the domain
separate from any machines running on the physical network. But the host
cannot see these machines. Local Only is an internal virtual network for
virtual machines only.

The client XP vm should get its network config automatically. Have you
authorized the DHCP service in AD? It will not hand out IP addresses to a
client until you do.

You can always configure the client manually. Give it a IP address in
the same IP subnet as the host (eg 192.168.0.2 netmask 255.255.255.0) and
the DC's IP address (192.168.0.1) for DNS.

Note that ping might fail because of the firewall settings on the server.
You need to enable ICMP echo for ping to work.

Thanks for your response. I've got some followup questions which I'll embed
within your post.

Oh, and sorry if I ask a lot of newbie questions. I'm trying to install it
so I can practice "managing" it. It's kind of backwards to me, but then
again, the MCSE exams start with "managing" and then move to "installing."

Thanks!

"Bill Grant" wrote:
I do not beleive I have authorized DHCP in AD (unless it's done
automatically upon installation). How would I go about doing this?
I believe I've tried this before, but it didn't work, maybe because DHCP
wasn't authorized?
How do I enable ICMP echo on the server?

See inline.

That really has nothing to do with VPC. That should be explained in the
notes on installing a domain controller.


A static config will override DHCP. A client will only broadcast on the
network with a DHCP discover message if it is set to obtain an IP
automatically.

That also has nothing to do with VPC. Look at the Windows Firewall
settings in Server 2003.