4
My current setup:
- VMWare Workstation 10.0.3
- Host OS is Windows 8.1 x64
- Guest VM is Windows 8.1 x64
- Host has 1 wired ethernet and 1 internal wireless NIC
- No antivirus (except windows defender) is installed
- Firewall on both the host OS and guest VM are turned off
What I'm trying to accomplish is to have the host OS use the wired ethernet to connect to an internal private network and the guest VM to use the wireless NIC in bridge mode to access the internet but still keep the host OS isolated from the internet.
I have followed the VMWare guide which instructed me to disable everything on the wireless NIC except VMWare Bridge Protocol
. I changed VMNet 0
from automatic bridging to bridge the specific wireless NIC and set my guest VM to use bridging. I connect to the wireless network from the host OS and then attempt to get a DHCP address inside the guest VM but it does not work. I even tried assigning a static IP and pinging the gateway which also does not work.
I tried uninstalling the wireless NIC drivers, reinstalling them, resetting the winsock catalog and ip stack, uninstalled and reinstalling VMWare, but nothing seems to work. I have also tried to connect to the wireless network through the same wireless NIC on the host (with all the appropriate protocols enabled) and the host is able to connect and pull a DHCP address from the router; it just will not work in the VM.
Any idea of what I'm doing wrong?
EDIT: The network topology over here is such that the internet facing network is wireless only and the private internal network is wired only, so testing the internet connection on a wired NIC isn't possible. Plus, this is a laptop and it only has 1 wired NIC so using something like an external wireless-to-ethernet bridge is out of the question.
I was using a wireless USB adapter and connecting that directly to the guest VM and this works but is a huge headache since over time, the USB adapter seems to stop working inside the VM and I constantly need to unplug the adapter, plug it back in and even sometimes have to go so far as to disable the device and re-enable it inside the guest VM's device manager (and yes, the drivers for the device are made for windows 8 and the device is fully compatible).
EDIT2: If it helps any, the wireless card is a Broadcom 802.11n and I'm guessing it's the BCM43XX chipset.
UPDATE If I leave everything checked in the wireless NIC properties (ipv4, ipv6, file sharing, etc...), the bridging works. As soon as I remove everything except the VMWare Bridge Protocol, it fails to work.
Bridging and wireless does not work well together. You should test with a wired network first to find out if the issue might be due to your wireless interface not supporting bridging. – kasperd – 2014-08-26T16:40:00.803
@kasperd unfortunately that isn't an option. The network topology over here is such that the internet facing network is wireless only and the private internal network is wired only, so testing the internet connection on a wired NIC isn't possible. Plus, this is a laptop and it only has 1 wired NIC so using something like an external wireless-to-ethernet bridge is out of the question. – vane – 2014-08-26T16:57:26.750
In that case, I'm guessing your wireless network does not support bridging. I'll recommend that you either route the traffic instead of bridging it or create an Ethernet over IP tunnel to a host with wired network and then bridge the virtual Ethernet interface in one end to your VM and in the other end to a physical wired interface. – kasperd – 2014-08-26T18:22:53.073
@kasperd If the wireless network doesn't support bridging, would that prevent an external hardware wireless bridge from connecting and working correctly? We had a printer connected to the wireless network through a wireless bridge device a few months ago and it worked fine. – vane – 2014-08-26T18:34:10.840
In that case the problem might just be the network interface. You can try connecting the the wired network interface to such a bridge, and configure the VM to bridge to the wired network interface instead. If that works, then chances are the wireless interface does not support bridging. If it doesn't work on wired network either, then chances are the VM configuration is wrong, and you need to reconfigure that until you get bridging to work on wired network before you try wireless again. – kasperd – 2014-08-26T19:08:07.463
@kasperd I tried bridging the wired connection in the exact same way that I did the wireless connection and it works fine. So my guess is that there is something wrong with the wireless NIC or driver. – vane – 2014-08-26T19:30:54.027