VMware Communities
jankerkenhoff
Contributor
Contributor
Jump to solution

Fusion 5.0.2 Network not working

Hey, got a Problem with Fusion 5.0.2 and Win 7 and Win 8 vms.

They both are not able to connect to the Internet. Bridged or NAT both dont work.

Tried a static IP adress ,also didn't work. Did a ipconfig /all lookup and it doesnt show a standardgateway, but setting it to the gateway of my mac doesnt help either.

Tried to run them under 5.0.1 also didnt help.

Any Ideas whats causing the Problem ?

Reply
0 Kudos
37 Replies
tracywang
Expert
Expert
Jump to solution

>Nope , it still dont works.

>I must have ticked that per acident. I am sorry, ist there a way to remove it ?

you should able to see the cancel the answered from the related comment.

Reply
0 Kudos
jankerkenhoff
Contributor
Contributor
Jump to solution

Seems like it keept the static ip config from a test before.

Here is the correct output :

Windows-IP-Konfiguration
   Hostname  . . . . . . . . . . . . : Jan-PC
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
Ethernet-Adapter Bluetooth-Netzwerkverbindung:
   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth-Gerät (PAN)
   Physikalische Adresse . . . . . . : 10-40-F3-F1-5D-11
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
Ethernet-Adapter LAN-Verbindung:
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MT-Netzwerkverbindung
   Physikalische Adresse . . . . . . : 00-0C-29-8C-FF-CC
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::9508:bbd7:abfd:fc26%11(Bevorzugt)
   IPv4-Adresse (Auto. Konfiguration): 169.254.252.38(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.0.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 234884137
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-3D-A9-6B-00-0C-29-8C-FF-CC
   DNS-Server  . . . . . . . . . . . : fd00::be05:43ff:fe89:2748
   NetBIOS über TCP/IP . . . . . . . : Aktiviert
Tunneladapter isatap.{07D5F36D-8574-45E8-81DE-837D4212A261}:
   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{FAA6C9B8-D53F-4531-9FE4-90D77CA5C41C}:
   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
Tunneladapter LAN-Verbindung* 4:
   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
turned of wifi and on , output unchanged and no internet connection
Reply
0 Kudos
tracywang
Expert
Expert
Jump to solution

Ok, it's a private address. Seems the dhcp is not working on your machine. Can you open Activity Monitor, and select All Processes, then enter "vm" in search box. Take a screeshot and attach here.

Reply
0 Kudos
jankerkenhoff
Contributor
Contributor
Jump to solution

Here the Processmanager screenshot you asked for:

Reply
0 Kudos
tracywang
Expert
Expert
Jump to solution

Ok, then can you run this in terminal:

ps aux | grep vmnet

and paste it here.

Reply
0 Kudos
jankerkenhoff
Contributor
Contributor
Jump to solution

The terminal output you asked for :

Jans-MacBook-Pro:~ Jan$ ps aux | grep vmnet
Jan            21096   0,3  0,0  2423356    200 s000  R+   12:03pm   0:00.00 grep vmnet
root            1079   0,0  0,0  2435156    180   ??  Ss    7:28pm   0:00.00 /Applications/VMware Fusion.app/Contents/Library/vmnet-netifup -s 7 -d /var/run/vmnet-netif-vmnet8.pid vmnet8 vmnet8
root            1077   0,0  0,0  2466888   1280   ??  S     7:28pm   0:00.28 /Applications/VMware Fusion.app/Contents/Library/vmnet-natd -s 7 -m /Library/Preferences/VMware Fusion/vmnet8/nat.mac -c /Library/Preferences/VMware Fusion/vmnet8/nat.conf
root            1074   0,0  0,0  2435264    212   ??  Ss    7:28pm   0:00.04 /Applications/VMware Fusion.app/Contents/Library/vmnet-dhcpd -s 7 -cf /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet1.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1
root            1072   0,0  0,0  2435156    176   ??  Ss    7:28pm   0:00.00 /Applications/VMware Fusion.app/Contents/Library/vmnet-netifup -s 7 -d /var/run/vmnet-netif-vmnet1.pid vmnet1 vmnet1
root            1069   0,0  0,0  2477820   2104   ??  S     7:28pm   0:00.09 /Applications/VMware Fusion.app/Contents/Library/vmnet-bridge
Reply
0 Kudos
tracywang
Expert
Expert
Jump to solution

That's what I expected.

Your output showed the dhcp process for NAT mode is not running. (from your screenshot, there is only one vmnet-dhcpd which is for vmnet1(host only mode), normally, there will be two vmnet-dhcpd running, vmnet 1 and vmnet 8.

So, please quit your Fusion. and relauch it. Before you run the VM, open the Activity monitor and check if there is two vmnet-dhcpd. (or using terminal to see if it is exist.

/Applications/VMware Fusion.app/Contents/Library/vmnet-dhcpd -s 7 -cf /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet8.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8

)

When this process is running, your networking should be ok.

If the vmnet 8 dhcpd is still not launch, I think there may be something to make it crashes. Try to swith to a new host account and run Fusion to see if the process is fine.

jankerkenhoff
Contributor
Contributor
Jump to solution

I restarted Fusion on my main profile and it was showing only one dhcp process.

I tried the same on a complete new profile, got the same result only dhcp process for vmet 1

Reply
0 Kudos
tracywang
Expert
Expert
Jump to solution

I suggest you clean reinstall the Fusion by these steps:

1. Quit Fusion

2. Delete

/Library/Preferences/VMware Fusion

/Library/Application Support/VMware

~/Library/Application Support/VMware Fusion

~/Library/Preferences/VMware Fusion

~/Library/Preferences/com.vmware.fusion.*

/Application/VMware Fusion.app

3. Reinstall Fusion by drag and drop the VMware Fusion.app to /Applications

Lanuch the Fusion and see if the vmnet8 is running.

(Please note, clean resintall will remove your license and any other preserence, please write down the License key at least)

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

As I already mentioned the other day "Anyway there is some interesting things in the support bundle however  I'm not going to have the time the next couple of days to investigate it  with Thanksgiving and holiday weekend."  however since I see you're being put through unnecessary hoop and jumps by tracywang I've taken the time to more thoroughly review the information in the support bundle and the system log shows the following:

Nov 21 14:31:13 Jans-MacBook-Pro.local vmnet-dhcpd[970]: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf line 46: expecting semicolon.
Nov 21 14:31:13 Jans-MacBook-Pro.local vmnet-dhcpd[970]: fixed-adress
Nov 21 14:31:13 Jans-MacBook-Pro.local vmnet-dhcpd[970]: ^
Nov 21 14:31:13 Jans-MacBook-Pro.local vmnet-dhcpd[970]: Configuration file errors encountered -- exiting
Nov 21 14:31:13 Jans-MacBook-Pro.local vmnet-dhcpd[970]: exiting.

Looking at "/Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf" it shows:

host windowserver2012 {
hardware ethernet 00:0C:29:BB:9E:BD
fixed-adress 192.168.166.120
}

And should be:

host windowserver2012 {
hardware ethernet 00:0C:29:BB:9E:BD;
fixed-adress 192.168.166.120;
}

Fix this with VMware Fusion closed and see if the DSLinux VM had connectivity then.

tracywang
Expert
Expert
Jump to solution

One more words:

Restart your Mac, after reinstall Fusion.

Reply
0 Kudos
tracywang
Expert
Expert
Jump to solution

Hi WoodyZ,

Why were you say: unnecessary hoop and jumps, did you read my comments 28? Don't you think a clean reinstall Fusion is the simplest solution than what a DSLinux.vmx do? You made a simple queston so complex...

Reply
0 Kudos
jankerkenhoff
Contributor
Contributor
Jump to solution

Deleted the host config completly solved the Problem.

Thank you for your help WoodyZ, especially while having on Thanks Giving over there.

Have a great Holiday and thanks.

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

If you had actually read the entire thread before jumping in you'd have a better handle on the situation!

VirtualBox works fine.

The DSLinux VM is to eliminate anything that may have been misconfigured in one of the Guests.  There is no sense in trying to diagnose an issue with an unknown entity (the existing VM's) and using a Linux Live OS such as this especially when it been previously validated to be know good and working and as a diagnostic/troubleshooting tool it is a way of helping to more easily isolate which direction to be looking.  It that to sensible of a concept?

What using DSLinux VM validated was regardless of whatever issue there may be in the existing VM themselves was irrelevant until it could be diagnosed what was the cause of VMware Fusion to not function properly before a VM was even started!

The reason I said "unnecessary hoop and jumps" is because, well you are! you're needlessly asking for information that is already in the support bundle and having him do things already done.

Had I more time the other day I would have more thoroughly review the support bundle, I just didn't, however it's reasonable now to assume that what I posted in Re: Fusion 5.0.2 Network not working is certainly part of the issue, if not the very issue itself.  I haven't finished reviewing the support bundle and it Thanksgiving Day here in the US, so I have other thing to attend to.

Message was edited by: WoodyZ - Originally posted, Nov 22, 2012 7:37 AM .

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

Jan, I'm glad it's all working for you and I'm sorry I just didn't have enough time to properly review the support bundle after you validated for me what area the issue laid by using the DSLinux VM the other day.

Have a good one! Smiley Wink

Woody

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Hi dear jan

Could you please tell what you did you done on the host exactly?

That will be very useful while i got the similar issue.

Thanks a lot.

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

What the issue was is that someone (possibly Jan) improperly manually edited the vmnet8 dhcp.conf file and as a result broke a segment of the VMware Virtual Network Infrastructure, as shown in my reply Re: Fusion 5.0.2 Network not working.  A proper resolution would be to edit the file correcting the mistakes made in coding or restore it from the backup one is suposed to make before manually editing such type files! Smiley Wink

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

thx WoodyZ,

I got it, the missing ";" ... :smileysilly:

Reply
0 Kudos