VMware Communities
firray
Contributor
Contributor

VMware Workstation Host Adapter/Nat Adapter not able to ping Guest OS and viceversa

I have observed that traffic from Guest PC is not replied back even though traffic is hitting the adapter.

I have Ubuntu 16.0.4 on which i have installed Vmware and then i have Guest OS from where i have attached the host only adapter or Nat adapter. In both cases  i can see guest is able to get IP address. In case of Nat adapter configured the device is able to reach any destinations outside the Ubuntu. If i try to access ubuntu resources no responses. I disabled firewall on ubuntu but still same result.

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01 

          inet addr:172.16.32.1  Bcast:172.16.32.255  Mask:255.255.255.0

          inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:102 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Vmnet Adapter Config

# Configuration file for ISC 2.0 vmnet-dhcpd operating on vmnet1.

#

# This file was automatically generated by the VMware configuration program.

# See Instructions below if you want to modify it.

#

# We set domain-name-servers to make some DHCP clients happy

# (dhclient as configured in SuSE, TurboLinux, etc.).

# We also supply a domain name to make pump (Red Hat 6.x) happy.

#

###### VMNET DHCP Configuration. Start of "DO NOT MODIFY SECTION" #####

# Modification Instructions: This section of the configuration file contains

# information generated by the configuration program. Do not modify this

# section.

# You are free to modify everything else. Also, this section must start

# on a new line

# This file will get backed up with a different name in the same directory

# if this section is edited and you try to configure DHCP again.

# Written at: 10/16/2018 16:14:14

allow unknown-clients;

default-lease-time 1800;                # default is 30 minutes

max-lease-time 7200;                    # default is 2 hours

subnet 172.16.32.0 netmask 255.255.255.0 {

        range 172.16.32.128 172.16.32.254;

        option broadcast-address 172.16.32.255;

        option domain-name-servers 172.16.32.1;

        option domain-name localdomain;

        default-lease-time 1800;                # default is 30 minutes

        max-lease-time 7200;                    # default is 2 hours

}

host vmnet1 {

        hardware ethernet 00:50:56:C0:00:01;

        fixed-address 172.16.32.1;

        option domain-name-servers 0.0.0.0;

        option domain-name "";

}

####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######

Tcpdump traffic

sudo tcpdump -i vmnet1

[sudo] password for firdous:          

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on vmnet1, link-type EN10MB (Ethernet), capture size 262144 bytes

05:01:39.825448 ARP, Request who-has 172.16.32.1 tell 172.16.32.129, length 46

05:01:41.829156 ARP, Request who-has 172.16.32.1 tell 172.16.32.129, length 46

05:01:43.829176 ARP, Request who-has 172.16.32.1 tell 172.16.32.129, length 46

05:01:45.829307 ARP, Request who-has 172.16.32.1 tell 172.16.32.129, length 46

05:01:47.833415 ARP, Request who-has 172.16.32.1 tell 172.16.32.129, length 46

Reply
0 Kudos
0 Replies