How do I fix VM player CentOS after latest host Windows 10 update?

[DavidCesi]

CentOS under Workstation player VM has worked for years until latest Windows 10 update.  Is this a coincidence?

when I ping 192.168.220.120 I get a 'Destination Host Unreachable' error

or if I try and access  192.168.220.120 as usual via Chrome under Windows 10 I get 'This site cannot be reached'  

Any insight gratefully recieved.

David.

[wila]

Hi,

Have you tried the following already?

Uninstall VMware Player

Reboot

Install VMware Player

As you are on Windows 10, you might want to use VMware Player 12.1 and not VMware Player 12.5 as the latter has some networking issues for some people.

--

Wil

[DavidCesi]

Hi

Its been a while. 

Did the uninstall reboot install thing with no luck

Tried upgrading but could only get the latest v12.  But I can now ping in Centos and get a positive result.  Meanwhile in Chrome under Win 10 it cant find the address ' site unreachable'

Any ideas?

[DavidCesi]

I am using VMWare player 12.5.2 build-4638234

[DavidCesi]

Windows command line ping gives 100% lost packets. (see attached)

[DavidCesi]

CentOS ping attached

[wila]

What does the IP address "192.168.220.120" stand for? The VM? Your host? Something else?

Is your VM connected via NAT/DHCP/host only?

--

Wil

[DavidCesi]

Hi Wil

Thanks for answering.

"192.168.220.120" is the IP address of a Wiki application running under CentOS

The network adapter is set to NAT (see settings attached)

David.

[wila]

Hi,

Ok, then the ping should normally still have worked. A firewall can stop this, so you might want to try to disable the firewall on Windows 10.

Alternatively if you run AVG antivirus there appears to be a setting in there that specifically blocks virtual networks.

At least I seem to recollect it was AVG antivirus having specific settings for that, I might be misremembering.

--

Wil

[DavidCesi]

Hi Wil

Dont use Windows or AVG firewall but I use Avast which is set to allow VMWare.  I tried to turning it off but that didnt make any difference. Also Tried adding VMWare exe path specifically to Avasts exclusion list with no luck. Cant find any settings specific to VNs ...

[wila]

Hi,

Sometimes just disabling antivirus isn't enough.

I've not used Avast in a long time, so can't really advise on any specific settings with it.

As your VM is having network access, this is one of the things i would look at.

Another would be to make sure that the VM is still using the IP address that you think it uses.

I'm having trouble reading the actual address on the VM in the screenshots almost looks like 192.168.228.128 instead of 192.168.220.120, but  did you try to ping itself there? That normally works.. a more interesting test would be if the guest can access something like google.com

--

Wil