Click on Virtual machine settings, under devices select network adapter, and then Network connection, select Bridged connection and click ok, Then test your connection.
That how I resolved my issue
destination host not reachable for VM instance on Windows 7 host
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
May 20, 2013
I am running VMWare Workstation 9 in a Windows 7 Professional host (on IP 192.168.1.103).
There is a running VMWare VM on fixed IP 192.168.1.99. The host W7 computer has, in the past, been able to ping the VM but this has recently stopped working. Pinging 192.168.1.99 from the DOS cmd (as administrator) window now reports "Reply from 192.168.1.103: Destination host unreachable".
There are no addressing conflicts on the network. The firewall has been turned off. (an external sub-net based machine is able to ping the VM )
Another computer on the sub-net (at address 192.168.1.102) is able to ping 192.168.1.99 (and vice versa).
The problem seems to be related to the loop back process associated with the host adapter. I believe that the problem appeared after a Microsoft Windows 7 Update was installed.
The VM networking is set to bridged and to replicate the physical network connection state.
Notes:
I have uninstalled and re-installed WMWare workstation.
I have re-installed the ethernet adapter driver.
I have cleared the host arp cache, although it did not have the desired 192.168.1.99 address in it.
If I force an entry for 192.168.1.99 on the adapter the message changes to 192.168.1.99 did not respond.
Here is the ipconfig /all from the host machine
Windows IP Configuration
Host Name . . . . . . . . . . . . : Roy-PC2012
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 84-8F-69-CC-3A-F8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7def:b714:2a4:7a05%25(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, May 19, 2013 11:06:38 PM
Lease Expires . . . . . . . . . . : Thursday, July 18, 2013 11:06:38 PM
Default Gateway . . . . . . . . . : fe80::226:5aff:feb8:d9dd%25
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::60f5:c853:d118:286e%26(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.211.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 436228182
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-26-D7-74-4C-EB-42-4C-3B-EB
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6818:1b53:9a8e:bda0%27(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.174.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 453005398
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-26-D7-74-4C-EB-42-4C-3B-EB
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{C18DDD35-9CDE-4EDE-A76B-B83F4C1670A3}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{8A67A32E-C4BF-4864-98D4-631EA6C73DF9}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{A7286BEC-0283-4A63-8E42-FB0BF3D5F007}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Windows for home | Previous Windows versions | Internet and connectivity
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
6 answers
Sort by: Most helpful
-
Anonymous
2017-11-10T12:44:16+00:00 -
Anonymous
2014-02-12T17:02:15+00:00 Win 7 Ping problem solved (by merging split network):
i had similar trouble - unable to ping win 7 PC to PC through a simple pocket switch (both PC's off network, manual IP and subnet, no DNS or DHCP), but I could take the same windows 7 PC and connect to an internet serviced network without a problem. The machine could ping itself, but not the other machine ("destination host unreachable")
i tried disabling IPV6, reconfiguring IPV4, netsh int IPV4 reset, netsh winsock reset, arp to edit and/or clear the routing tables, installing "simple TCP/IP services", working with HomeGroup, disabling firewalls, and editing firewall policies. None of these efforts fixed the ping problem
Solution was related to a split network on the win 7 machine. Under public networks, there was an option to "Merge or Delete network locations." Selecting that option then showed that two networks existed on the Win 7 machine: "Network" and "Network2". There was an option to select both and "Merge" - i merged the two networks into one, and the ping immediately started working.
-
Anonymous
2013-05-20T21:24:18+00:00 Another update,
I have now talked to 14 different people from Microsoft. On the 13th person we did a joint call to VMWare to discuss the issue. VMWare solidly pointed the finger at Microsoft and would not help with resolution unless they were paid for support. The Microsoft person said that Microsoft would look further into the problem without charging for it (much appreciated).
I was told I would get a call back this afternoon at 1PM. The call from the 14th Microsoft person came in at 2PM. He tried to suggest that this was a VMWare problem and that I would have to call them. I explained that we had already gone down that route (he backed off on blaming VMWare). I am now expecting a follow up from Microsoft at 8:00AM tomorrow.
I will continue to update.
-
Anonymous
2013-05-20T15:15:30+00:00 Hi Greg,
Finding someone else with the same problem is helping my sanity. I was having this same problem a month or so ago and it was remedied by reverting to a "pre-windows-update" restore point. This restore point has since been replaced by a more recent (after the problem has occured) restore point. So, I can't undo the updates this time.
I am now venturing into the world of Microsoft support. I am now getting directed to Pro Support after explaining my problem to 7 different people and getting dropped once. (no exaggeration, its not needed). I am now talking to the "Consumer Team" and I am about to get re-directed to the Business Team.
I will post the result :)
-
Anonymous
2013-05-20T09:11:01+00:00 Roy,
I am having the same problem. Ping, DNS fails to work between host and guests on the same machine. Everything works fine between guests on the same machine. Everything works fine between separate machines on the same network to the host and guests and vice versa. Gateway and Internet connection work for all scenarios.
Everything was working fine several days ago and then just stopped working. Nothing has changed on this machine except the updates from Microsoft that I know of.
I did the same thing as you by disabling firewalls, uninstalling and reinstalling VMware Workstation, etc., to see if I could get it to work.
All my guest development servers cannot be connected to from my host which all the development tools are installed on. Setting up a guest O/S with development tools to work around the problem.