Not able to ping host OS from guest OS and vice-versa

[SaurabhSood]

Hi All,

I have installed Oracle Enterprise linux 5 on vmware 2 , host OS is windows 7.

But I am not able to ping my host and guest OS from each other.

Following is the output of , ipconfig /all :

==================================

C:\Users\Sood>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Sood-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Atheros AR8151 PCI-E Gigabit Ethernet Con
troller (NDIS 6.20)
   Physical Address. . . . . . . . . : 60-EB-69-F1-89-60
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Atheros AR9002WB-1NG Wireless Network Ada
pter
   Physical Address. . . . . . . . . : 68-A3-C4-1C-8B-77
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e4ce:d3f6:38a1:5261%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.101(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, January 12, 2012 10:54:42 AM
   Lease Expires . . . . . . . . . . : Thursday, January 19, 2012 10:54:41 AM
   Default Gateway . . . . . . . . . : fe80::218:e7ff:fefe:f768%11
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a9d6:7567:3ea0:3c5f%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.131.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 419450966
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-82-92-9A-68-A3-C4-1C-8B-77

   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 VMnet
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8dd:82e:4c32:5ca7%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.110(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 436228182
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-82-92-9A-68-A3-C4-1C-8B-77

   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.{1FB422A5-B3FA-429C-B681-DA3478A6FB96}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{7674F9D9-8422-4482-9F2A-8A6B73856BC8}:

   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 Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{C74B92D3-9942-4722-BC25-1C8868CFC363}:

   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

===============================================================

Following is the output of ifconfig -a:

==================

[root@cloud1 network-scripts]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0C:29:7C:BE:ED 
          inet addr:192.168.0.110  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe7c:beed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11566 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7347 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15915643 (15.1 MiB)  TX bytes:651876 (636.5 KiB)
          Base address:0x2000 Memory:d8920000-d8940000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3663 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3663 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4152132 (3.9 MiB)  TX bytes:4152132 (3.9 MiB)

sit0      Link encap:IPv6-in-IPv4 
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@cloud1 network-scripts]#

==========================

[root@cloud1 network-scripts]# service iptables status
Firewall is stopped.
[root@cloud1 network-scripts]#
=============================

I am using Bridged networking.

Any help on this will be appriciated..

[WoodyZ]

I have installed Oracle Enterprise linux 5 on vmware 2

First of all there is no VMware Product named "vmware 2" so while I could guess what you mean by "vmware 2" nonetheless I'm not going to waste my time.  Always include the full VMware Product Name Version Number and Build Number and post in the proper Forum.

==========================

[root@cloud1 network-scripts]# service iptables status
Firewall is stopped.
[root@cloud1 network-scripts]#
=============================

Okay so the Guest's Firewall is turnned off but what about the Host as Windows 7 by default blocks ICMP Echo Requests (ping).

I am using Bridged networking.

The Host's Physical Network Adapter's Subnet (Atheros AR8151 PCI-E Gigabit Ethernet Controller) is 192.168.0.0 and so is the VMware Virtual Ethernet Adapter for VMnet 8 and this (VMnet 😎 should be assigned an IP Address in a different Subnet.  This is probably causing conflicts between the Physical Subnet ad the Virtual Subnet since they are assigned then same IP Address Subnet.

Host Physical IP Address: 192.168.0.101

Host's VMware VMnet 8 IP Address: 192.168.0.110

Bridged Guest's IP Address: 192.168.0.110

Normally the last octet of the Host's VMware VMnet 8 IP Address would be 1 as in 192.168.0.1 and not the same as the Guest's IP Address as shown in your ipconfig and ifconfig output.  Also since you say your using Bridged the Host's VMnet 8 IP Address and the Host's Physical Network Adapter cannot be on the same Subnet as shown by the ipconfig and ifconfig output.

So the bottom line you need to correct the configuration as it stands so it doesn't conflict as it now does.

[milton123]

In order to use bridge mode you have to use same block ip address. But Network Adapter VMnet1: you use different IP block which is not possible  for bridge mode. Here is a example of IP subnet you can use..

Ethernet adapter Local Area Connection:

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

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter VMware Network Adapter VMnet1:

IPv4 Address. . . . . . . . . . . : 192.168.0.xx  (Preferred)

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

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

DHCPv6 IAID . . . . . . . . . . . : 419450966

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-82-92-9A-68-A3-C4-1C-8B-77

Ethernet adapter VMware Network Adapter VMnet8:

IPv4 Address. . . . . . . . . . . : 192.168.0.110(Preferred)

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

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

Cheers, Yours Udin

[WoodyZ]

milton123 wrote: But Network Adapter VMnet1: you use different IP block which is not possible  for bridge mode.

@milton123  VMnet 1 has nothing whatsoever to do with this issue!  Base on what the OP said, the VM is using a Bridged Network Adapter and in this case, assuming VMware Defaults, the VM would use VMnet 0 and this VMnet never shows in the ipconfig/ifconfig output.  Additionally regardless of what the Guest is actually using there is a conflict in that the Host's Physical Network Adapter (Atheros AR9002WB-1NG Wireless Network Ada
per) and the Host's VMware Virtual Ethernet Adapter for VMnet 8 are on the same Subnet and by default VMnet 8 is NAT and would be an entirely different IP Address Subnet then that of the Physical LAN the Host is a part of.  Add to this that both the ipconfig output for the Host's VMware Virtual Ethernet Adapter for VMnet 8 shows it as 192.168.0.110 and the Guest's ifconfig output shows its IP Address as 192.168.0.110 this is improperly configured and conflicts with each other.  Therefore SaurabhSood needs to do as I have already said and that is to properly configure things and what you've presented is for the most part totally irrelevant and the only thing you said relevant was "In order to use bridge mode you have to use same block ip address" and this happens automatically when the Guest is configured as Bridged and is using DHCP in the Guest.  If the User manually configures the network Adapter in the Guest, as it appears, it cannot conflict with the IP Addresss already assigned to the Host as it does based on the ipconfig/ifconfig output!

@SaurabhSood  No offense intended towards milton123 however you can pretty much ignore what milton123 has said as VMnet 1 isn't applicable.

[SaurabhSood]

Thanks WoodyZ ....

I am using VMWare Server Version 2.0.2

Windows 7 ICMP echo request is not blocked. I have created a rule under windows firewall's advanced settings, to unblock any ping request ICMPv4.

As per your suggestions, Vmnet8 is corrected on windows7 and now it is like :

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::e4ce:d3f6:38a1:5261%11
   IPv4 Address. . . . . . . . . . . : 192.168.0.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::218:e7ff:fefe:f768%11
                                       192.168.0.1

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::a9d6:7567:3ea0:3c5f%14
   IPv4 Address. . . . . . . . . . . : 192.168.131.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::8dd:82e:4c32:5ca7%15
   IPv4 Address. . . . . . . . . . . : 192.168.78.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

But Still I am not able to ping the host OS from guest OS.

I have configured another guest on same host and both the guest OS are able to ping each other, but not to the host OS.

Any help will be appriciated...

Thanks,

Saurabh Sood

[SaurabhSood]

Hi,

Now I am seeing that windows is able to ping the guest OS and guests also able to ping the windows machine.

But still cannot find, why suddenly it has happened???

Could you point me the mandatory things that are must, so that guest and host ping each other

Any idea about this?

Thanks,

Saurabh Sood