Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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'.

share|improve this question

closed as off topic by Sven, MDMarra, Michael Hampton, mgorven, EEAA Feb 28 '13 at 5:25

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

This is not the proper site for this question, see the FAQ. It might fit on Super User, but check their FAQ and archive first. – Sven Feb 28 '13 at 2:15
@SvenW Seriously I don't understand why it's not the right site. FAQ mentions "network routing" and "virtualization". I know this is not a production server, but it IS a dev server, and I AM developing in a professional capacity. I just happen to have holes in my understanding of networking, and I'm looking to learn about it. – user162199 Feb 28 '13 at 2:25
Why did you have to bring operating system religion and browser wars into this? There's enough hate in the world already without adding all this. – gecko Feb 28 '13 at 3:40
@meetamit dev setups are off topic. If you're not a sysadmin, chances are your question it off topic here. Dev tools are on topic on SO though. – MDMarra Feb 28 '13 at 3:51
from the FAQ: and ist not about ... Anything in a home setting. Dev systems are off-topic as well. Also, I will never understand why people want to argue about topicality if they are even pointed to a better place to ask the question. – Sven Feb 28 '13 at 3:52
up vote 0 down vote accepted

Bridged networking

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.

share|improve this answer