On that same line, it would be worth checking to make sure none of your private subnets are conflicting with each other either. I am not entirely certain what it looks like in OS X land, but under Windows VirtualBox adds a "VirtualBox Host-Only Network" that if you disable or generally muck with, it causes no end to weird problems. Or even better, add a different network adapter type (Maybe Intel instead of PCNet or vice versa).įourth, try statically assigning an IP address in your guest as to minimize the host networking issues.įifth, make sure the various VirtualBox adapters in your HOST are enabled and configured right. Third, as suggested, remove the existing network adapter in your VM configuration and re-add it. They usually live where the virtual machine XML configuration file lives. Im pretty sure that youre wrong when you say you were able to be in bridged mode while not using a cable. Second, have you looked in the log files VirtualBox generates? It will likely give you (or those trying to help) clues as to what is happening. Virtualbox (cant say for VMWare but it should be similar) isnt able to virtualize a wireless card and cant share the wireless card of your machine with the host OS. 3.1.2 is out and 3.1.4 is in beta (at the time of this posting). There are probably several things working against you:įirst, upgrade your version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |