virtualbox.org

Ed,

It seems to me that with all of this you simply need to setup you guests just a little differently than what you are using.
Let me explain a few things then you can decide if you want to proceed or not.

The IP address range of 192.168.56.* is reserved for the VirtualBox host-only service
The IP address range of 10.0.2.* is reserved for the VirtualBox NAT service.

So If you want to setup a computer LAB you have a few choices.

• If you are not going to be doing a Domain you would use Bridged and assign fixed address within the same IP range as the host and your router.
• If you are going to do a domain I strongly suggest that you use the Internal service (which emulates a network switch) Using a non route-able IP address range
• You can then add a second adapter to the guest set to NAT for updates, or you can add an additional guest to become your router.
• You can use the host-only service as well and add a second adapter set to NAT in any guest that requires Internet access.

The only thing that I can see that is stopping you from succeeding is you are mixing up the address ranges. They can't be mixed or they will conflict and of course not work.

So maybe if you could define for me what you are wanting we can figure out the right approach.

I understand what Ed is attempting to do, as I am having the same issue (with version 4.1.6), where I am setting up multiple guest OS environments that are dependent on each other as well as needing to have access to the outside world.
The User Manual states "A virtual machine with NAT enabled acts much like a real computer that connects to the Internet through a router..." Unfortunately vbox v4.1.6 doesn't appear to work that way.

While each individual OS is able to access the 'outside world' and somehow VBOX is able to route the packets appropriately, the problem is that under the virtual NAT environment, rather than each guest OS being given a unique IP address within the DHCP subnet range, all are being given the same IP default IP address of "10.0.2.15", thereby disabling an co-dependent OS functionality in a muitple guest OS environment.

There may be a 'work around' but hopefully this will be resolved in the next release..

@pandarus,

What you are stating is by design. What is your actual need/requirement? What are you trying to do?