I would like to ping one vmware guest from another one. Both are Windows XP and use NAT. I set IP manually for VMnet8 to 192.168.18.1. (no using Obtain IP address automatically). Also I'm not able to ping neither guest1 nor guest2 from host.
I'm using VMWare Player 5.
Host machine (Windows 7):
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::dc81:34e2:779d:595d%19
IPv4 Address. . . . . . . . . . . : 192.168.18.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Guest 1:
Connection-specific DNS Suffix . : localdomain
IP Address. . . . . . . . . . . . : 192.168.18.131
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.18.2
Guest 2:
Connection-specific DNS Suffix . : localdomain
IP Address. . . . . . . . . . . . : 192.168.18.132
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.18.2
Any suggestions?
Thanks!
I just ran into the exact same problem while configuring my server 2008 and windows 7 vm's in
VMware workstation 9. what helped is disabling the firewall and running the following command at the windows command prompt
netsh firewall set icmpsetting 8 enable
at that point I was able to ping one VM then both once I performed the command on both. this differnce between our scenarios is I have my VM configured using Bridged connections
You can ping ip from one virtual machine to another machine by using these steps:
- Go to menu VM -> Setting -> select network adapter: NAT
- Go to menu VM -> setting -> select options Tab and select
Guest Isolation : ENABLED, ENABLED and select box : ENABLE VMCI
- Try installing VMware tools in guest operating system.
- Check if firewall is enable
- If 1 and 2 are ok, try using share internet connection
After sharing connection the VMnet8 IP address will be changed to 192.168.137.1
, set up the IP 192.168.18.1
and try again
I know it is an old question, but I had a similar trouble recently. On VMware Workstation 12.+ go to Edit -> Virtual Network Editor...
Select a network used by the problematic VM and make sure that "Connect a host virtual adapter to this network"
checkbox is set for this network. In my case, it was not. After it was set, the host was able to ping the guest and guests were able to talk to each other.
I have been able to ping from VMs and the host by setting the VM's network settings to "Bridged" mode. This, in short, places them all on the same physical network. This coupled with your static IP addresses should do the trick.
In Menu bar
select the Host-> Virtual Network Settings -> Host Virtual Network Mapping...
set your drop down list as your host Network Adapter...If You can not ping Check your Firewall Status Because the Firewall is blocked the 'ping' packets
If i am understanding your question. You now have both VMs on the same network segment VMnet8,
- Enable file and print sharing from the firewall settings on both VMs
- Ensure that from the host machine (Windows 7) that the network adapter for VMnet8 is enabled. Also open the network adapter to check if you are actually connecting to VMnet8 network address. Then try to ping both addresses.
- If this still doesnt work, perform ipconfig/all from host machine and paste the output here so that i can see how the network address are distributed.
Thanks
On both Operation Systems, must turnoff firewall.
I using MS SERVER 2012 R2 & MS WIN-7 as a client. First of all call "RUN BOX" window logo button+ R, once RUN box appeared type "firewall.cpl" at Window Firewall setting you will see "Turn Window Firewall On or Off" like this you click it & chose "turn off window firewall" on both Private and Public Setting then OK. Ping again on guests OS.
GOOD-LUCK
Aungkokokhant
I would like to add, that yes. While using the NAT adapter settings in Vmware and turning off windows firewall I was able to ping other guest machines in my test environment.
Sidenote: Best practice would be to implement a hardware firewall in larger environments and turn off windows firewall on the Domain Controller.
I came to the same problem and tried all methods on internet, and finally worked it out by accident. May you could try this(see in the picture)