Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 193198

Getting rid of Unidentified Network in Win7 VM on CentOS5 host with VMware Player 4

$
0
0

Hi,

 

I'm running a Windows 7 VM on a CentOS 5.8 host with VMware Player 4.0.4, the network type is NAT. Often (not always) I notice that Windows recognises two networks, one named as "Unidentified Network", the other one as "Network". In these cases the Unidentified Network is assigned to Windows' network adapter and the Windows VM does not have any network connectivity.

 

The Unidentified Network appears after an unattended installation of Windows (not funny if you try to put the Windows VM into a domain) and often after I ran Windows updates which require a reboot.

 

Normally I can solve this issue by disabling/enabling the Windows network adapter or by rebooting the VM.

 

I've searched the internet up and down to find a solution which would avoid the VM to get connected to the Unidentified Network, without success.

 

As far as I understand, the Unidentified Network comes from VMware's host only network adapter vmnet1. My idea was to somewhat disable vmnet1, so I set the IP address range in /etc/vmware/vmnet1/dhcpd/dhcpd.conf to something out of range, as proposed here. Since this did not help, I set the lease time to 0. This did not help neither, so I renamed the whole directory /etc/vmware/vmnet1/. When checking vmware-networks --status, I can see that the DHCP server for vmnet1 is not running, but I still get the Unidentified Network in the Win 7 VM (and vmnet1 still shows up if I run ifconfig).

 

I've been working on this for two days now, so any help or idea to get rid of the Unidentified Network in the Windows 7 VM would be highly appreciated!


Viewing all articles
Browse latest Browse all 193198

Trending Articles