VMware Communities
kopseng
Enthusiast
Enthusiast
‎02-09-2021 04:04 AM
Jump to solution

Lost Networking after Upgrading Windows 10 Pro to 20H2

I have been using VMWare 15 for the last two years on my current well specked desktop computer. Today the networking bits of my Ubuntu VM (20.04 LTS) stopped after rebooting the host OS for the cumulative 20H2 "service pack". I have been trying for hours to get the networking back:

- I removed the network adapter in VMWare, rebooted Windows, added it started up again (and variations thereof)
- I have completely uninstalled VMWware (apart from config and license), downloaded afresh and installed 15.5.7 build-17171714
- Changed networking setup from NAT to Bridge and back
- Removed-added networking adapter again

No go. Dropping down to the terminal in Ubuntu after a fresh reboot of the guest os and typing `curl github.com` just hangs without anything happening.

0 Kudos
1 Solution

Accepted Solutions
LarsiDarsi
Contributor
Contributor
‎02-11-2021 11:26 AM
Jump to solution

i had same problem after upgrading VMware from a previous version to 16.1 and Update my host to Windows 10 to 20H2.

My solution for all bothered users. Done in Workstation:

1. Click "Edit" -> "Virtual Network Adapter"

2. Click "Add Network"

3. Select a Network Adapter to add: "VMNET0"

4. Click "OK"

5. In "Virtual Network Adapter" select your pevious added network adapter "VMNET0"

6. Click right down "Change Settings"

7. In "VMnet Information" choose your connection type

8. In my case i use "Bridged" and select my WIFI-Network Card

9. Click "OK"

Thats all. Good luck.

Regards Lars

View solution in original post

5 Replies
ender_
Expert
Expert
‎02-09-2021 02:37 PM
Jump to solution

Have you tried Edit → Virtual Network Editor… → Change Settings → Restore Defaults ? That should reset VMWare's networking.

0 Kudos
kopseng
Enthusiast
Enthusiast
‎02-10-2021 12:51 AM
Jump to solution

I tried resetting, as described. Made no change 😕 Could there be something in the Ubuntu setup that indicates something wrong? This is the output from `ifconfig`:

br-83f4eb0aadf9: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:2a:d4:a7:af  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-94056ff603fe: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 172.20.255.255
        ether 02:42:e9:e6:70:fb  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-c818660d2e63: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.24.0.1  netmask 255.255.0.0  broadcast 172.24.255.255
        inet6 fe80::42:4dff:fe0a:16e9  prefixlen 64  scopeid 0x20<link>
        ether 02:42:4d:0a:16:e9  txqueuelen 0  (Ethernet)
        RX packets 9  bytes 468 (468.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 68  bytes 7946 (7.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:8dff:fe15:91ab  prefixlen 64  scopeid 0x20<link>
        ether 02:42:8d:15:91:ab  txqueuelen 0  (Ethernet)
        RX packets 27  bytes 2112 (2.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 62  bytes 7165 (7.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.247.128  netmask 255.255.255.0  broadcast 192.168.247.255
        inet6 fe80::20c:29ff:fe52:199c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:52:19:9c  txqueuelen 1000  (Ethernet)
        RX packets 148  bytes 10949 (10.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1539  bytes 143285 (143.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 255  bytes 73740 (73.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 255  bytes 73740 (73.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth1d09898: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::4881:a0ff:fefc:4172  prefixlen 64  scopeid 0x20<link>
        ether 4a:81:a0:fc:41:72  txqueuelen 0  (Ethernet)
        RX packets 9  bytes 594 (594.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 92  bytes 10914 (10.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth4ef0c5b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::904b:e4ff:fefe:6865  prefixlen 64  scopeid 0x20<link>
        ether 92:4b:e4:fe:68:65  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 92  bytes 10929 (10.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth6d22bc8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::f00f:44ff:fee2:23fe  prefixlen 64  scopeid 0x20<link>
        ether f2:0f:44:e2:23:fe  txqueuelen 0  (Ethernet)
        RX packets 27  bytes 2490 (2.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 97  bytes 11274 (11.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethc03b721: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::ac82:8dff:fe17:84aa  prefixlen 64  scopeid 0x20<link>
        ether ae:82:8d:17:84:aa  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 92  bytes 10929 (10.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
0 Kudos
kopseng
Enthusiast
Enthusiast
‎02-10-2021 12:55 AM
Jump to solution

Even doing `sudo` has problems, which to me might indicate issues with routing to `localhost`?

Output from `route` (notice it hangs for 20 seconds before outputting anything!):

$ time route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    0      0        0 ens33
link-local      0.0.0.0         255.255.0.0     U     1000   0        0 ens33
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-83f4eb0aadf9
172.20.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-94056ff603fe
172.24.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-c818660d2e63
192.168.247.0   0.0.0.0         255.255.255.0   U     0      0        0 ens33

real	0m20,024s
user	0m0,003s
sys	0m0,000s

 

This is /etc/hosts:

$ cat /etc/hosts
#F5 Networks Inc. :File modified by VPN process
127.0.0.1	localhost web.localhost admin.localhost
127.0.1.1	ubuntu

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters


# Time suck
127.0.0.2   www.facebook.com www.nrk.no nrk.no tu.no db.no vg.no  www.db.no www.vg.no www.ap.no ap.no aftenposten.no www.aftenposten.no tu.no www.tu.no www.tek.no www.dn.no www.dagbladet.no

127.0.0.3   web.ptflow.no admin.ptflow.no

#  https://www.kodemaker.no/blogg/2020-04-hack-slack/
slack-redir.net cleanredirect.appspot.com

 

0 Kudos
LarsiDarsi
Contributor
Contributor
‎02-11-2021 11:26 AM
Jump to solution

i had same problem after upgrading VMware from a previous version to 16.1 and Update my host to Windows 10 to 20H2.

My solution for all bothered users. Done in Workstation:

1. Click "Edit" -> "Virtual Network Adapter"

2. Click "Add Network"

3. Select a Network Adapter to add: "VMNET0"

4. Click "OK"

5. In "Virtual Network Adapter" select your pevious added network adapter "VMNET0"

6. Click right down "Change Settings"

7. In "VMnet Information" choose your connection type

8. In my case i use "Bridged" and select my WIFI-Network Card

9. Click "OK"

Thats all. Good luck.

Regards Lars

kopseng
Enthusiast
Enthusiast
‎02-16-2021 07:13 AM
Jump to solution

For some reason, after installing yet another 20H2 update, the network started working again. At least, all the way until I restarted the VM. Then it was back to its old tricks. Following LarsiDarsi's recipe did work, though! Although, on my VMWware 15.5 installation, the terms are not quite the same: 

  • Virtual Network Adapter is called Virtual Network Editor
  • There was no "Change Settings": the settings (including VMNet Information) were displayed inline with all other settings
0 Kudos