I guess this was the third time I fell into this trap, so I document it here (mainly for myself):As long as you have any kind of LAN type interface/adapter active under Windows VirtualBox will try to use this[1] to do its networking (NAT in my case). This is true for LAN/Ethernet as well as WLAN/Wifi.
This also happens quietly, so you don't get an error message (from VBox), just the errors from the guest OS, usually DNS errors, because thats likely the first thing to fail.
In my case I frequently run on 3G/HSPDA only, but still have an active (yet disconnected) LAN and WiFi interface. In order for VirtualBox to work properly, those two have to be disabled.
Annoying...
Hope I remember it next time.
-----
[1] or so it seems.
Subscribe
No comments:
Post a Comment