On Thu, 29 Oct 2009 14:37:01 -0700, dbere
>>Thanks for the reply,
>>The domain controller does provide the dns, and all firewalls are off. One
>>of the first things I tried, I'm not sure what the fact that I can only ping
>>one way means.
>Have you selected the host NIC or Shared Networking for the VMs
>>I tried both, neither works. There are two other settings, local and
>>something I can't think of at the moment, that didn't do the trick either.
>>Host NIC works for the std edition.
If you want to connect the guests to the host domain controller then
the only two possible networking options are to use the host NIC or
Local Only. Windows networking does not allow NAT or ICS for
networking if you want to attach a PC to an AD domain.
If you go the Local Only way then you need to set up the host with a
Loopback adapter sitting on the same network as the guests, I think.
But back to your connectivity issues:
If you have a situation where the guests can ping (and get response
from) the host and you are not using NAT or ICS, then you actually
have a working connection. If it works one way it works the other way.
TCP/IP is not unidirectional...
So the failure for the ping towards the guests would come down to HOW
ping <guest ip address)?
ping <guest computer name>?
The second ping requires a working DNS system that can resolve the
computer name and I doubt very much that you have that. It will not
come on by default...
So please first test the ping by IP address and report back.
If that was what you did then the next possibility is packet filtering
on the guest and firewalls. Out of the box new Windows operating
systems always refuse to reply to ping so it has to be enabled in
Windows. Where depends on how it is blocked, firewall is one place and
advanced network interface options another.
Bo Berglund (Sweden)