VMware Communities
cloudsavy
Contributor
Contributor

VMware - Destination host unreachable

Hello experts,

I have a situation here, I configured two VMWare workstations viz rac1 and rac2 both have eth0 configured as bridged connection. when i ping the other workstation (rac1 to rac2 & viceversa) it is showing me an error

From rac2 (192.168.0.200) icmp_seq=709 Destination Host Unreachable

when i ping rac2 from rac1

it is blank... no output!

Information about my system:

Windows IP Configuration

Wireless LAN adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::c4ea:3bc0:bd22:ded0%13

   IPv4 Address. . . . . . . . . . . : 192.168.0.50

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::789e:d29a:13af:3b4d%23

   IPv4 Address. . . . . . . . . . . : 192.168.1.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::e152:56eb:5b7:ba1a%24

   IPv4 Address. . . . . . . . . . . : 192.168.28.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 14:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{B3D86355-B8BB-4798-8C9E-5B8E2A72735F}:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{D3FCA9E6-957F-4C2A-A286-08A644C19262}:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{B2C2C3DF-4F86-4ED3-A1AF-6D53B65EACA9}:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

I'm using a wireless LAN internet.

Windows 8, VMWARE Workstation 7.0.0 build-203739

Kindly help me to resolve this.

Message was edited by: a.p. - changed title from all caps

Reply
0 Kudos
5 Replies
a_p_
Leadership
Leadership

Welcome to the Community,

as a first step check whether the VMs are able to ping their gateway address (192.168.0.1). If this doesn't work, make sure your wireless router allows multiple connections from the same physical system.


André

Reply
0 Kudos
cloudsavy
Contributor
Contributor

Thanks for the reply andre, when i pinged gateway 192.168.0.1 it is still showing destination host unreachable. kindly advise what to do.

Reply
0 Kudos
a_p_
Leadership
Leadership

As mentioned before, you may need to check whether your wireless router allows multiple connections through the same physical wireless adapter.

If there's no requirement to access the VMs from other external systems, consider to switch to NAT networking which should not have any issues (regardless of the physical adapter).

ndré

Reply
0 Kudos
anif
Contributor
Contributor

what is OS in your VM (Linux)?

check your VM network status first (if you use linux you can use command ifconfig), UP or DOWN?

from your VM can you ping to your Host (IP 192.168.0.50)?

If not then you need to check network adapter status in VM (UP/DOWN)?

if network adapter UP, check your bridge configuration in vmware workstation configuration (maybe you pointing to wrong network adapter)

Reply
0 Kudos
cloudsavy
Contributor
Contributor

Thanks for all your support, yes it was up, could find fault... did few things and it is working now.

1) installed vmnet bridge protocol ---> vmnet0 --> properties --->check vmnet bridge protocol

2)updated & reinstalled wireless adapter driver

3)reinstalled vmware & its n/w components

Thanks you anif & a.p 🙂

Reply
0 Kudos