I "upgraded" from Fusion 6.0.4 to 6.0.5, and now bridged networking no longer works in Windows VMs.
The VM gets an IP address:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : attlocal.net
Link-local IPv6 Address . . . . . : fe80::315d:97cf:b800:a2cb%10
IPv4 Address. . . . . . . . . . . : 192.168.1.76
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
but pings to the router (192.168.1.254) time out.
The VM is Windows 7 with VMware Tools 9.6.2. I tried reinstalling Tools, but nothing changed.
I tried switching from bridged (autodetect) to bridged (wifi). Nothing changed.
I tried "ipconfig /release" and "ipconfig /renew". Nothing changed.
I have multiple Windows 7 VMs with bridged networking. They all fail in the exact same manner.
NAT networking works fine in the Windows VMs.
Bridged (autodetect) networking works fine in my OSX VM (ping router, surf web, etc).
The host networking also works fine (ping router, surf web, etc).
The host is a MBP 15" with 16GB RAM and OSX 10.9.5.
Everything worked fine before upgrading to 6.0.5, so the problem is directly related to 6.0.5 and Windows VMs.
Suggestions? Thanks.