VMware Communities
GeoffWild
Contributor
Contributor
Jump to solution

Networking not working to 1 Ubuntu VM

Running on Win 11 pro, VM Ware Pro Version: 17.5.0 build-22583795

For some reason, my main Ubuntu VM has a ? in the network icon and I can't access anything.  
Tried shutting down, disconnected the connection, reconnect - to no avail.

I created a 2nd VM machine, both are configured the same - the 2nd is connected - but the 1st won't anymore - it used to work.

Any ideas?

0 Kudos
1 Solution

Accepted Solutions
GeoffWild
Contributor
Contributor
Jump to solution

Both vm's are the same in Network editor, NAT.

ip a

Not working:

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:50:56:3b:6b:62 brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.61.132/24 brd 192.168.61.255 scope global dynamic noprefixroute ens33
valid_lft 1764sec preferred_lft 1764sec

Working:

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:cb:76:15 brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.61.133/24 brd 192.168.61.255 scope global dynamic noprefixroute ens33
valid_lft 939sec preferred_lft 939sec

 

I dropped the HW compatibility to 16.2, upon reboot, I noticed that systemd-resolved was disabled.  Restarted, and now the network is working and no longer have a ? over the network icon.

Very strange.


View solution in original post

0 Kudos
3 Replies
louyo
Virtuoso
Virtuoso
Jump to solution

Not working provides little information. What does not working mean?

Nat or Bridged?

What does ipconfig/all show on host?

What does ip addr show in working versus non-working VM?

Any differences in Network Editor on VM's?

 

GeoffWild
Contributor
Contributor
Jump to solution

Both vm's are the same in Network editor, NAT.

ip a

Not working:

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:50:56:3b:6b:62 brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.61.132/24 brd 192.168.61.255 scope global dynamic noprefixroute ens33
valid_lft 1764sec preferred_lft 1764sec

Working:

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:cb:76:15 brd ff:ff:ff:ff:ff:ff
altname enp2s1
inet 192.168.61.133/24 brd 192.168.61.255 scope global dynamic noprefixroute ens33
valid_lft 939sec preferred_lft 939sec

 

I dropped the HW compatibility to 16.2, upon reboot, I noticed that systemd-resolved was disabled.  Restarted, and now the network is working and no longer have a ? over the network icon.

Very strange.


0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution

Odd - usually the 00:50:56 prefix mac addresses are used when having static IPs, while the 00:0c:29 ones are used when having DHCP.