virtualbox.org

hi all, I am trying to simulate a simple network that contains a two domain controllers. I have my network mode on the default NAT and I haveset the ip address on the vm's to 10.0.2.15 and 10.0.2.16 respectively and used the gateway ip 10.0.2.2
I am trying to make the DC on x.x.x.16 to replicate what I add to the DC on the x.x.x.15 but found no success. It can not even resolve it even though the setting for the dns was set to the first DC ip address.
On trying to resolve connectivity issues, I tried pinging the gateway from both machines and that was a success, however, when i try to ping the either machine from the other i receive a timeout. what is it I am doing wrong? do I have to change the IP's on the machines or do I have to change the networking mode??

I am confused by the networking section in the user guide because it is very vague to me! it would have been alot easier if it was explained in what operates in which OSI layer rather than just words! your help would be appreciated.

kind regards

You need to use Bridged instead of NAT for this.

Perryg wrote:You need to use Bridged instead of NAT for this.

Dear Perryg,
I must admit that I am somewhat confused by the networking section of the manual, I am not clear on what works in which layer of the OSI model and hence I can not visualise how it actually work for me to be able to trouble shoot or design a network according to a rooted understanding of how the networking section is working.
Excuse me if my questions might sound elementary to people with experience of the software but I am trying to understand as to why I should be using one set up rather than the other.
If I select bridged networking then I lose the gateway address from the setup. In NAT by default, software default that is, the gateway is at 10.0.2.2 and as i understand it, up to the gateway (in NAT), everything works in layer 7 until communication is needed with the outside world then things will start to function on a layer 3 level with a single virtualbox operating in a PAT fashion? (single ip multi-port to keep track of guests).
I, therefore, do not understand why a NAT setup can not be used to build a network within virtualbox(so to speak) that would contain a number of machines that would use the same default (per software) network id of 10.0.2.x (x being 15 up to and including 254).
It seems that my understanding of the way the software operates is somewhat wrong, since i could not achieve such a setup.
my setup needs a collection of machines (DC's+clients) to be able to be set on the same private network ID and these machines need to be able have full connectivity and cross talk.
Can someone please shed some light on what to use and how does the solution work? as in how does it function and interacts? I hope that you would find the time to answer such a query because it is confusing. I can make machines ping eachother by trial and error (with regard to the network operating mode) but I need to undestand what would work and how &why is the internal gateway address in virtualbox (10.0.2.2)is lost once i no longer use NAT?

Fitouri wrote:why is the internal gateway address in virtualbox (10.0.2.2)is lost once i no longer use NAT?

Because thats part of VBox NAT implementation, use Bridge and you then use the same the Host is using. ea. your router.

vbox4me2 wrote:[

Thanks for taking the time to reply. My host system is not attached to a router. I am connecting to the internet using a vodaphone USB mobile internet stick. so that means my Ethernet network card is not attached to anything and hence not used. that is why I was seeking an understanding of networking with VB so as to facilitate the best solution for what I have, in short machines being on the same net ID and the host being able to connect to them.

In this situation you would need the first adapter in NAT mode to be able to get to the Internet and then a second adapter using Host-only.
Then you would be able to have guest-to-host and host-to-guest communication.