• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Solved Cannot ping Ubunto guest in vmware player


geoB

New Member
Posts
13
#1
In Win8.1 Pro as host, with vmware player 6.02, Ubuntu 12 or 14, server or desktop guest:

Network adapter set to Bridge.The guest OS installs just fine. Guest gets an IPv4 address from DHCP server on the same subnet as the host. Guest can connect to the Internet for downloads. Host connects to the Internet. Yet a ping from host to guest or guest to host results in destination unreachable. Occurs even if NIS "smart firewall" is turned off.

I've used essentially the same setup with a Win7 host with no issues. Any clues why the two won't talk to one another?

[fwiw, I bounced off Hyper-V when I saw how sluggish it was compared to vmware player. Hope it's not the better solution!]

George
 
Last edited:

My Computer

System One

  • OS
    Win10Pro
    Computer type
    PC/Desktop

jimbo45

New Member
VIP Member
Guru
Hafnarfjörður IS

Posts
4,373
#2
Hi there

1) Check your router -- some routers block Ping
2) Check firewall on LINUX guest -- probably best while testing to turn it off -- people forget that default Linux installs - especially for the common distros (Ubuntu, Debian, Fedora, Mint, OPENSUSE) have the Linux firewall enabled. - I'll bet a lot of people are surprised that Linux even HAS a built in firewall !!!

3) Does the ping work when you Ping via hostname or are you pinging via IP address. I've had an instance where pinging by Hostname gives the WRONG IP address -- re-boot simply fixed that.

4) IPV6 might be in the mix somewhere but this isn't normally a problem on internal LANS - in any case Host name resolution should fix this.

(BTW for Linux sharing SAMBA is excellent -- there's a good GUI tool for Ubuntu type distros (debian based). I think it's called system-config-samba. Saves all the messing about with configuration files althougk you WILL need to add users via sudo -a usename for the users you want for your shares).

How to configure Samba using a graphical interface in Ubuntu | Unixmen

Cheers
jimbo
 

My Computer

System One

  • OS
    Linux Centos 7, W8.1, W7, W2K3 Server W10
    Computer type
    PC/Desktop
    Monitor(s) Displays
    1 X LG 40 inch TV
    Hard Drives
    SSD's * 3 (Samsung 840 series) 250 GB
    2 X 3 TB sata
    5 X 1 TB sata
    Internet Speed
    0.12 GB/s (120Mb/s)

geoB

New Member
Posts
13
#3
Thanks for the reply.

There is an alternate explanation, but without a solution...yet. The desktop box is connected to my LAN via wireless adapter. So even though ipconfig (see below) shows it is disconnected, I have connectivity via Network Bridge (the MS multiplexor). If I disable the wireless adapter & connect via hard wire, I am able to ping the virtual machine.

According to VMWare:
"Bridged networking with a wireless Ethernet adapter is supported in VMware Workstation 4 and later, VMware Player 3, VMware Server, and GSX Server 3 on Windows hosts." I don't know whether this means that only VMWare Player 3 will connect, or Player 3 and later will connect.

Oddly, if I log in to the router (a SonicWall TZ 170) I can ping the vm just fine. But not the IP of the desktop's bridge. So here's the rub.

It is not yet convenient to connect via hard wire. More to be learned.


ipconfig output:Windows IP Configuration


Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::60b1:62c9:c836:eb2%20
IPv4 Address. . . . . . . . . . . : 192.168.0.145
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.168.168

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

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::4cff:ec7c:d24c:338f%29
IPv4 Address. . . . . . . . . . . : 172.16.138.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::ec88:d24d:302b:be24%30
IPv4 Address. . . . . . . . . . . : 172.16.80.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
 
Last edited:

My Computer

System One

  • OS
    Win10Pro
    Computer type
    PC/Desktop

geoB

New Member
Posts
13
#4
It was indeed the pesky network bridge. Disabling it, plus setting the properties of the wireless NIC allowed pinging, etc., with the virtual machine. So, what's the point of the network bridge?

g
 

My Computer

System One

  • OS
    Win10Pro
    Computer type
    PC/Desktop