VirtualBox Internal Network (expedition part 1: begins)

This post was republished to All Things IT in a Nutcrack... at 03:44:30 PM 2010/12/20

The expedition begins….

I’ve decided to do a fresh install of VB 3.2.12 to see if there is anything I missed…(RTM…that would also help a great deal)

The first thing I noticed… was that from previous versions to this one – the network component is marked clearly:

Virtual networking – Bridged Networking & Host-Only Networking

This then brings back the question: How do you get the “Host-Only” networking to work in such a way that you can run an internal network.

Remember my setup:

Host runs Windows 7, with 4GB Ram,

Guests run Windows XP, Windows 2008 R2, Windows 2003 each with 20GB VDI, 1024Mb Ram.

At any point, I would like to run two virtual machines (as I can with VMWare Server)

Simple, right?

Expedition part 1 continues….

But….when you start to configure components yourself…..

Internal Network Setup:

Virtual Machine Host 1 -

Virtual Machine Host 2 –

Windows 7 Networking

VirtualBox Preference Settings

The moment you try to enable the DHCP server on the Host-Only Adapter – it hangs….

After some tweaking and testing….and crash dumping, its now back and allows me to configure the whole thing….

All Things IT in a Nutcracker's Shell