I (unfortunately) have a Windows XP instance running in VirtualBox on my Mac, which is running a dev server (Node.js connect).
I’m successfully able to access the dev server from the VM’s browser (which is, tragically, IE8), using the host’s ip address, BUT only when my WiFi is connected to one of the two networks I’ve tried this on.
I.e., when I’m connected to an Airport Express router, it works fine. But it doesn’t work when I’m connected to the router at home (sorry, I can’t recall the router’s make ATM; it’s a cable modem supplied by Optimum).
So, am I correct in thinking that the router is playing a role in whether or not access is possible? And, what would I need to do to make it work?
Happy to supply more info if needed.
P.S. I’m pretty sure this was the right forum to ask this Q – rather than StackO’ – but if I’m wrong, please don’t be hatin’.
This is for more advanced networking needs such as network simulations and running servers in a guest. When enabled, VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system’s network stack.
On Macintosh hosts, functionality is limited when using AirPort (the Mac’s wireless networking) for bridged networking. Currently, VirtualBox supports only IPv4 over AirPort. For other protocols such as IPv6 and IPX, you must choose a wired interface.
I assume you have read the man pages for virtualbox? Let us know what you’ve tried, as it helps.