host only network not working

[morpheus2011]

Hello,

my host only network is not working since a few days. Before that it worked.

I've updated from 4.0.1 to 4.0.2, but I don't know if this is the reason.

Striking is the IP address from the host. This was before 192.168.106.1. Now it is in the link-local area.

my data:

VMware Player 4.0.2 build

Host: Windows 7 Professional

Guest: Ubuntu 10.04 LTE, VMware Tools up to date, static ip 192.168.106.12

ipconfig /all

Windows-IP-Konfiguration

Ethernet-Adapter VMware Network Adapter VMnet1:

   Verbindungsspezifisches DNS-Suffix:

   Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1

   Physikalische Adresse . . . . . . : 00-50-56-C0-00-01

   DHCP aktiviert. . . . . . . . . . : Nein

   Autokonfiguration aktiviert . . . : Ja

   Verbindungslokale IPv6-Adresse  . : fe80::cdae:b6fb:1b1a:3ceb%23(Bevorzugt)

   IPv4-Adresse (Auto. Konfiguration): 169.254.60.235(Bevorzugt)

   Subnetzmaske  . . . . . . . . . . : 255.255.0.0

   Standardgateway . . . . . . . . . :

   DHCPv6-IAID . . . . . . . . . . . : 352342102

   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-15-A7-9D-90-F0-DE-F1-70-70-68

   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1

                                       fec0:0:0:ffff::2%1

                                       fec0:0:0:ffff::3%1

   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

[milton123]

  IPv4-Adresse (Auto. Konfiguration): 169.254.60.235(Bevorzugt) 

Look here the Ip address is a gurbase IP address. It will not work. I think your DHCP is not working. Please have a liik followings link DHCP setup will be clear..

http://superuser.com/questions/126319/how-do-i-config-a-host-only-network-in-vmware

milton 

[a_p_ · Accepted solution]

I agree with the other poster. Please check whether the "VMware VMnet DHCP Service" (vmnetdhcp.exe) is running. You could also try to do a "Restore Defaults" to see whether this solves the issue.

André

[morpheus2011]

vmnetdhcp.exe running.

"Restore Default" and re-configure (as vmnet.PNG in the appendix) was the solution.

The cause of the disorder, however, remains unclear.