5
I created a new VM, and was able to ping it using its IP address. However, I can't ping it by name - even though it belongs to the same "WORKGROUP" as my other windows machines. What makes this particularly strange is the result of the following command:
C:\>ping -a 192.168.0.20
Pinging WIN-AOHA8MSD3D0 [192.168.0.20] with 32 bytes of data:
Reply from 192.168.0.20: bytes=32 time<1ms TTL=128
...
So the machine name can be queried, as indicated above, but when I turn around with that name it fails:
C:\>ping WIN-AOHA8MSD3D0
Ping request could not find host WIN-AOHA8MSD3D0. Please check the name and try
again.
In case it is relevant, the VM is in VMWare Workstation 7.1 using a bridged network adapter. The guest OS is Windows 2008 R2 SP1. The host is Windows 7 x64. Originally the ping of the IP address had not worked either, but I had created an ICMP rule on the guest OS that allowed the echo request.
What is necessary to make the machine name "pingable?"
The network discovery piece was all that was necessary. However, I "fixed" it differently than directed by the link you provided. I went into Windows firewall advanced settings on the guest, and enabled half of the already existing inbound network discovery rules. Instantly I could access the guest by name from the host. I disabled the network discovery rules, and the host (not surprisingly) continued to access the guest by name. – Brent Arias – 2011-06-20T16:23:50.367