Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 16635
  • Last Modified:

vmware guest can't ping host, can ping all other network devices

Hi.  
I have VMWare Workstation 10 host running on a Windows 8 PC.  I have a guest VM running XP.    This is a new installation of VMWare Workstation, and a newly created VM.

The host can ping every device on the the network/domain except the VM.  The VM can ping every device except the host.  

Networking for the VM is set to "bridged".   Firewalls and AV are off on both.

Any ideas why I can't ping the host from the VM ?
Thanks
Capture.JPG
0
Rob Rudloff
Asked:
Rob Rudloff
  • 12
  • 7
  • 5
  • +2
7 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you change to Host only can you ping the host ?

are the VM and Host on the same network, do they receive IP Address via DHCP or Static ?
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
if you change to Host only can you ping the host ?
I'm not sure I get what you're asking ...
are the VM and Host on the same network, do they receive IP Address via DHCP or Static ?
Static IP's on both Host and VM, both on same network.  This network is not DHCP.
Also, this VM is on the actual PC where Workstation is installed & running.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Change the VM Networking to Host Only.

and then try and ping the host.

Have you checked the IP Addresses are different, correct Subnet Mask?
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
Rob RudloffIT Development SpecialistAuthor Commented:
"Host Only" doesn't seem to fix pinging the host.  (In that scenario, the guest VM can't ping the host, or anything on the network.)

IP addresses are different, and the subnet seems correct -- When set to "Bridged, both Host and VM can ping every device on the network, except each other (being on the same machine).  
Other devices on the network can ping both the Host and the running VM.  
Both Host and VM have access to files on the domain file server.
1
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, I would expect the VM not to be able to ping devices on your LAN, in Host Only mode, hence why it's called Host Only mode, communications is only between Host and VM (and vice versa).

What error message do you get from ping?

timed out ?

both mac addresses are different, in Host and VM ?

use ping and check arp tables, to confirm firewall is not blocking...

This is a WIRED Ethernet connection and not WIRELESS?
0
 
John HurstBusiness Consultant (Owner)Commented:
Also, on your Bridged Setting, try unchecking Replace network state.  I have that unchecked when I use Bridged Connections and do not have an issue.

Also, in addition to your tests with Host Only, try setting to NAT to see if NAT works. I use NAT on my Windows 8 laptop and ping back forth works.
0
 
John HurstBusiness Consultant (Owner)Commented:
@RobRud  - Did you have any success?  

If Bridged Networking won't work, you can stop (shut down) all your machines, uninstall VMware Workstation, restart and install VMware Workstation. That can fix Bridge Network errors.

If you do this, run TCP/IP reset on your host machine as well.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Restart the computer
1
 
Rob RudloffIT Development SpecialistAuthor Commented:
UPDATE:  I contacted VMWare Support, and they spent about 3 hours connected to the PC.   In that time, they uninstalled Workstation, scrubbed it out of the Registry with a 3rd-party tool, and reinstalled.  This had no net effect.
They monkeyed with the network settings for the VM and changed some settings for the VMWare Virtual Networks (I missed seeing what they changed, but the results are in the 3 screen captures attached.)

They were blaming something on the wireless network vs. the wired ethernet network settings -- I'd be surprised if that was really the case, having had lots of exposure to "XP Mode" in Windows 7, where I have always just enabled "Bridged Mode" and everything works, no matter what adapter or network I am on.

To answer some of your questions:

Originally I was at my office on a wired network with a domain.  Both Host and Guest VM exist in the domain, and can ping other devices on the network, but can't ping each other.   Pings timed out.
Currently, I am at home, using DHCP, with the same results -- I can ping and use other devices on the network, and ping google.com from both Host and Guest VM.   However, Host and VM can't ping each other (time out).  Here you can see me pinging the router and a printer, but no sign of the host pings at 192.168.1.5

C:\Documents and Settings\robrud>arp -a
Interface: 192.168.1.7 --- 0x2
  Internet Address      Physical Address      Type
  192.168.1.1           00-7f-28-2a-23-39     dynamic
  192.168.1.99          f4-81-39-30-b9-4f     dynamic

Any other suggestions?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If this is a WIRELESS CARD, as I questioned, there are KNOWN issues with WIRELESS DRIVERS that do not bridge correctly.

So are you using a wireless connection or wired ?

and if VMware Support cannot get it working, and they've remote access.........
0
 
John HurstBusiness Consultant (Owner)Commented:
At this point, temporarily install VMware Workstation on another machine, copy a problem machine over to the temporary machine and try Bridged Networking.

If that works, then the host machine operating system may have been corrupted somehow. Did you do a TCP/IP Reset and Restart of the Host machine?
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
Currently this is a wired Ethernet connection.   Both at home and at the office.  I tried wireless at home, just to see if there was a difference.

I will install Workstation 10 on another machine, and copy the VM there, just to see if it works there.  I'll post results here soon.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
OK -- I copied the VM to another PC running Workstation 10, on another network.  
Same results:  The VM and Host can ping everything on the network, except each other.
I set the Network to Bridged, and tried both "replicate state" on and off.
I also did a trick that the VM Support guy did, and removed/added the virtual network adapter for the VM.  It installs a fresh "VMware Accelerated AMD PCNet Adapter".

UPDATE:  VMWare support tried adding a second network adapter to the VM, and set it to the "Host Only" network.  That worked, in that I could ping the Host at it's new "Host Only" network address (192.168.40.xxx).  However, that is not a prefect solution, as certain software we use really want to see the host on the corporate network (10.9.8.xxx).  
The support guy seemed perplexed, and is still looking for a solution -- he feels Bridged should work as it does in Win 7's "XP Mode".

Anything else I could try?  
(We have about a hundred of PC's like this, and it would be really handy if we could get it working, and good for VMware, I'd say.)
0
 
John HurstBusiness Consultant (Owner)Commented:
On the new setup, try making a new machine.  So different PC, new installation of VMware Workstation, and now new test machine. I think that should work and if it does, it means a problem with the existing guest machine.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's the network driver in the PC which does not supported the function.

Try getting a newer driver, same issue observed with certain wireless nics.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
Yes, I plan on trying a brand new VM from scratch on that other PC.
I will look for new NIC drivers now ...
I'll post my results.
Thanks.
0
 
Black_FlagCommented:
When I see this happen it usually is a DNS issue.  Did you create a static host record for that machine in DNS by chance?  If you, i'd do that and i bet it works.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
Yes, I looked in DNS and verified that the Host and VM are in there.   I have a network guy here, and he is confused too, since we can so a "net view" of the host from the VM.   We did an bunch of command-line commands, the results of which I've pasted below.  (The host machine is at 10.9.8.74 called "rob-vaio", the VM is 10.9.8.75 "rob-winxp", the domain is called "rsbco.local").  There you can see that I ping the host by name, and DNS resolves the IP address, but the ping doesn't get there.

I installed Workstation on my PC at home (completely different hardware, standard Verizon Fios DHCP router), created a new Windows XP VM from scratch.  I get the same results -- The VM is at 192.168.1.52, and it can ping and be pinged by all devices on the network, except the host.  Is it me ... What am I doing wrong?    VMware Support promises that it should work simply in "Bridged" mode.
==============================================
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

-------------------------------------------------------
H:\>ping 10.9.8.74
	Pinging 10.9.8.74 with 32 bytes of data:
	Request timed out.
	Request timed out.
	Request timed out.
	Request timed out.
	Ping statistics for 10.9.8.74:
	    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

-------------------------------------------------------
H:\>set
	ALLUSERSPROFILE=C:\Documents and Settings\All Users
	APPDATA=C:\Documents and Settings\robrud\Application Data
	CommonProgramFiles=C:\Program Files\Common Files
	COMPUTERNAME=ROB-WINXP
	ComSpec=C:\WINDOWS\system32\cmd.exe
	FP_NO_HOST_CHECK=NO
	HOMEDRIVE=H:
	HOMEPATH=\
	HOMESHARE=\\RSBCO.local\files\users\robrud
	LOGONSERVER=\\RSBDMC2
	NUMBER_OF_PROCESSORS=1
	OS=Windows_NT
	Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32
	\WindowsPowerShell\v1.0
	PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1
	PROCESSOR_ARCHITECTURE=x86
	PROCESSOR_IDENTIFIER=x86 Family 6 Model 60 Stepping 3, GenuineIntel
	PROCESSOR_LEVEL=6
	PROCESSOR_REVISION=3c03
	ProgramFiles=C:\Program Files
	PROMPT=$P$G
	PSModulePath=C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\
	SESSIONNAME=Console
	SystemDrive=C:
	SystemRoot=C:\WINDOWS
	TEMP=C:\DOCUME~1\robrud\LOCALS~1\Temp
	TMP=C:\DOCUME~1\robrud\LOCALS~1\Temp
	USERDNSDOMAIN=RSBCO.LOCAL
	USERDOMAIN=RSBCO
	USERNAME=robrud
	USERPROFILE=C:\Documents and Settings\robrud
	windir=C:\WINDOWS
	

-------------------------------------------------------
H:\>ping -a 10.9.8.6
	Pinging RSBdmc1.RSBCO.local [10.9.8.6] with 32 bytes of data:
	Reply from 10.9.8.6: bytes=32 time<1ms TTL=128
	Reply from 10.9.8.6: bytes=32 time<1ms TTL=128
	Reply from 10.9.8.6: bytes=32 time=1ms TTL=128
	Reply from 10.9.8.6: bytes=32 time<1ms TTL=128
	Ping statistics for 10.9.8.6:
	    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
	Approximate round trip times in milli-seconds:
	    Minimum = 0ms, Maximum = 1ms, Average = 0ms


-------------------------------------------------------
H:\>ping localhost
	Pinging Rob-WinXP.RSBCO.local [127.0.0.1] with 32 bytes of data:
	Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
	Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
	Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
	Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
	Ping statistics for 127.0.0.1:
	    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
	Approximate round trip times in milli-seconds:
	    Minimum = 0ms, Maximum = 0ms, Average = 0ms


-------------------------------------------------------
H:\>ping rob-envy
	Pinging rob-envy.RSBCO.local [10.9.8.74] with 32 bytes of data:
	Request timed out.
	Request timed out.
	Request timed out.
	Ping statistics for 10.9.8.74:
	    Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),

-------------------------------------------------------
H:\>net view \\rob-envy
	Shared resources at \\rob-envy
	Rob's HP Envy
	Share name  Type  Used as  Comment
	----------------------------------
	Users       Disk
	The command completed successfully.


-------------------------------------------------------
H:\>net use \\rob-envy\ipc$
	The command completed successfully.


-------------------------------------------------------
H:\>ping 10.9.8.74
	Pinging 10.9.8.74 with 32 bytes of data:
	Request timed out.
	Request timed out.
	Request timed out.
	Request timed out.
	Ping statistics for 10.9.8.74:
	    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

-------------------------------------------------------
H:\>tracert 10.9.8.74
	  Tracing route to rob-envy.RSBCO.local [10.9.8.74]
	  over a maximum of 30 hops:
	  1     *        *        *     Request timed out.
	  2     *        *        *     Request timed out.
	  3     *        *        *     Request timed out.
	  4     *        *        *     Request timed out.

H:\>

Open in new window

0
 
John HurstBusiness Consultant (Owner)Commented:
I installed Workstation on my PC at home (completely different hardware, standard Verizon Fios DHCP router), created a new Windows XP VM from scratch.  I get the same results

That sounds completely unreasonable. I have been using VMware Workstation since V1 on all kinds of computers and connecting / pinging between host and guest in bridged mode has never ever failed.

I wonder if you have a corrupt copy of VMware Workstation. You can download again, make a note of the MD5 checksum and then use DigestIT 2004 or other tool to verify the checksum.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
John --
Actually, I used different downloads at home and at my office.  Also, the version at the office was one or two "sub-releases" older when I discovered it was not working -- VMware support uninstalled the old version, uninstalled any remnants of Workstation and Player left behind, then reinstalled the later version ... same results.

What version # are you using?
0
 
John HurstBusiness Consultant (Owner)Commented:
Hello Rob,

I am using Version 10.0.3 Build 1895310 currently but I have used all versions and sub-versions along the way. I know this current version works properly for bridged mode connections as well as NAT connections. I use both.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
It looks like VMWare Support has thrown in the towel :

Hello Rob,

Thank you  so much for the update.

Hope you have tried pinging the host from a different computer on the network. We would like to thank you for bringing the issue in to our notice, we will reproduce the issue internally and if we are able to reproduce the issue, we will engage our internal team on the same.

Since we are temporarily able to workaround the issue by adding a secondary NIC and the networking type as Host Only. Can we go-ahead and archive the support request?

I look forward to hear from you.
0
 
John HurstBusiness Consultant (Owner)Commented:
It looks like VMWare Support has thrown in the towel : if we are able to reproduce the issue, we will engage our internal team on the same.

I have never seen this issue (15 years of use) so it would not surprise me if they cannot reproduce this.
0
 
Rob RudloffIT Development SpecialistAuthor Commented:
Found it.
I started uninstalling everything on my home PC.   My company uses Barracuda VPN --- the client "Barracuda NAC" is installed on both my PC's.   When I removed this software, my VM could ping it's Host (and vice-verse).  Next, I reinstalled the NAC software, and found it stuck an adapter into the Ethernet network connection.  This thing is called "Secure Personal Access Client" (see attached screen cap).  With it on, it causes the problem in VMware.  Unchecked, everything works fine with VMware.  (In fact, it seems to have no effect on my VPN connection either, so it will stay off until someone at Barracuda tells me it has to be on)
Screenshot-2014-08-19-19.18.33.png
1
 
Rob RudloffIT Development SpecialistAuthor Commented:
Problem was VPN software that was installed on both of my test PC's.  Problem was not VMware, but the adapter/protocol that is added to all the existing NIC cards / network connections upon installation of the "Barracuda NAC 3.5" VPN software.
0
 
Jitendra GandhiCommented:
Thanks RobRud
I have uncheck npcap for network property and my problem solved
0
 
Jitendra GandhiCommented:
Thanks
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 12
  • 7
  • 5
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now