Our remote users normally connect to our private network using the built-in Mac VPN; our private network uses the 172.16.x.x IP range. When we recently installed Fusion 3.x (with WinXP Pro as guest OS) on a MacPro running Snow Leopard, the host OS was still able to connect using the VPN but received only timeouts when trying to access any of our hosts resident on our private network (even though the VPN connection was established). This behavior only began post Fusion install and occurs with or without Fusion running. The original Fusion install was for NAT; we tried bridged, but with no change to the behavior. Later we tried host only networking, but, again, no effect.
I asked this user to kill all of the virtual interface processes (via Activity Monitor) to determine if they could be the source of the problem. When he did this, he found that he was able to access our private network resources normally.
We tried to disable the launchd process com.vmware.launchd.vmware.plist - it runs /Library/Application Support/VMware Fusion/boot.sh - but Fusion failed to start altogether.
Upon further investigation, it looks like the virtual interfaces are using the same IP space (172.16.x.x) as those on our private network. Is it reasonable to assume that this is the source of the problem? If so how can it be fixed in a reproducible way, one that survives reboots?
