I have been nagged for a while to upgrade to 12.5.8 from my 12.5.7 and today I decided to comply...
Result:
When I start up my Ubuntu 16.04.3 Server it won't connect to the network, so I am limited to use the VMWare WS console rather than SSH into it...
This means I cannot copy the console output and paste here so I have to limit myself to what I can type.
This is what I see:
$ ifconfig -a
ens33 Link encap:Ethernet HWAddr 00:0c:29:28:3f:b8
inet6 addr: fe80::2c:......./64 Scope:Link
-- Cannot type the remaining stuff ---
ifconfig used to return eth0 and it should have a DHCP given address too since on my network it has a reservation on the router/dhcp server.
My network does not use IPv6, so why the ipv6 address is shown is beyond me.
I have set the network interface to use bridged networking because I need network access to the virtual machine from my own PC, which is the VMWare host, and hence I cannot use NAT. Prior to updating to 12.5.8 this worked fine.
Another issue:
When I started up the guest there was a message saying I need to update the VMWare tools. So I tried this and found that I had to manually go through some steps to do this, but when I finally could start the install script it said that it had detected distribution native tools and it was recommended to use that instead. Strange that it put out this notice at the bottom on the VMWare window about updating the tools...
Anyway I aborted this and now I am stuck with a server not connecting to the network. I have rebooted the guest a couple of times but there is no change.
Can someone please help with some instructions solve this while noticing that the Ubuntu machine is a server that does not have a GUI, only a console.
Got it going at last!
At first I followed the advice in this webpage to change the interface name back to eth0.
Then I rebooted the guest as stated but nothing changed regarding connectivity.
After a lot of fiddling I finally decided to shut down all of my work processes and reboot my Windoiws 7 X64 PRO PC.
Amazingly this made the networking come back on! ![]()
But when i upgraded from PRO 12.5.7 to PRO 12.5.8 there was no mention that a reboot of the host machine was needed!
Well I talked too soon! :smileyangry:
It turns out that now this Ubuntu 16.04.3 LTS guest as well as all others too have lost their network connections!
To me this looks like a serious bug in the PRO 12.5.8 version, at least when running in a Windows 7 X64 Pro workstation like mine!
This time, what triggered the issue (at least this is what I believe) is that I configured DHCP on my router (an ASUS RT-AC68U) to reserve IP addresses for the bridged guests.
When I applied this the router sort of recycled and the network connections went down for a few seconds.
After this nothing network wise works on the VMWare Workstation PRO 12.5.8 anymore, not even closing and starting it again makes the guest networking work..
Last time (when I started this thread) the problem was initiated by me upgrading WS PRO12 to the latest version 12.5.8 and since it did not suggest that a restart was needed I proceeded but got these errors. A full system restart worked to get back to normal.
But now I have the same situation without even changing anything at all in PRO12, when the router network glitch happened both running guests lost their network connection and it was not fixed by rebooting the guests nor by restarting PRO12!!
QUESTION:
Can I downgrade to PRO12.5.7, which has worked fine for a long time? Or am I hosed after upgrading to 12.5.8?
Now I must close all of my working windows and reboot my whole system just to see if this will solve anything.
What a pain!
After the reboot I will test and then report back here.
OK, verified!
When I restarted Windows 7 and then VMWare PRO12.5.8 I could start the guests and get them to connect to the network!
So:
Why does the guest networking get lost if there is a glitch in the host networking caused by the Internet router reconfiguration?
Surely it should at least be restored if VMWare PRO12 is closed and then opened again? But this does not happen....
Something is keeping networking off on the guests in this situation until I reboot the host (which I do not want to do because it breaks up all of my work stuff).
I have tried this but all of it has failed:
- Suspend the guest and then resume it
- Disconnect/Connect the guest's network adapter
- Guest reboot
- Guest shutdown, PRO12 close, then start PRO12 and fire up the guest
The only thing that did work:
- Shut down guest, Shut down PRO12, reboot Windows7, Start PRO12, Start guest
This is a usability nightmare!
