IP address in Windows VM using NAT mode

[Owenhawk]

Running a Windows XP SP3 vm in the latest Fusion on Mac Book Pro.  We VPN into our organization on the Mac and want the Windows VM to also be connected seamlessly to the VPN.  Using NAT mode, the standard vmnet8 adapter and ip address is showing up when you do an ipconfig in the Windows VM, which is a 192.168 address. Problem is our firewall software running in the VM sees the VM as not on the trusted network (because of the 192 address), even though the host is VPNed in on a trusted network.  Is there some way to make Fusion give the VM the VPNed in IP address that the host has?  FYI, in the VM when the firewall is running, dns and wins are pingable but the domain is not.  As soon as the firewall is disabled, then the domain can be accessed.  We know there are other workarounds also, like use bridged mode and utilize multiple tokens to establist two vpn sessions, one on the Mac and one on the VM.  Thanks for any information.

[WoodyZ]

Using NAT mode, the standard vmnet8 adapter and ip address is showing up when you do an ipconfig in the Windows VM, which is a 192.168 address.

The vmnet8 Network Adapter is on the Host and it's IP Address cannot possibly be appearing in the output of the ipconfig under Windows.  The vmnet8 Network Adapters IP Address shows when running ifconfig in a Terminal under OS X.

Anyway from the sound of things this really isn't a VMware Fusion issue and if you cannot adjust settings in the other then VMware Fusion software like the AntiVirus, Firewall or VPN software then going Bridged, if the Server will allow it, is probably going to be what you'll have to do.

[Owenhawk]

Thanks. Sorry, I must have gotten the ip wrong, but what we need is for the Windows VM to display the IP address once the MAC VPNs in so that the firewall software won't complain. We don't have the option of changing how the firewall behaves unfortunately.  Bridge mode is definitely an option, but it will require our users to switch back and forth between the Mac and the VM being VPNed in or giving them 2 tokens.