Srv 08 R2 DNS,AD-DC internal network issues

[Vioxm1]

I realize that there is most likely a post regarding my issue somewhere in this thread, but after reading the first 3 pages of a 49 page search, I figured it would be better for me to post this and be referred to another page or get true feedback.
I am currently testing software for a local college that requires the use of Active directory and I do not wish to use our existing network for security reasons. After installing three guests into VB and configuring one server as AD and DNS I cannot seem to get the internal network setting in VB to realize the connection between all three guests. Have I missed a step? Because of DNS and static IP, DHCP is not something I want, or is it? Ether way when I try and join my other guests to my AD, they can't seem to find it.
Backing up a bit...
AD-DC and DNS is on one SRV08R2, Application SRV08R2 is on another, and WIN7 pro is on another, all sitting on a Win7 pro Host. all guest should be connected to internal network without access to internet or host.
Any thoughts please assist.

[Sasquatch]

Chapter 6 of the User Manual is a good reference. And the network tutorial in the Using VB part of the Tutorials and Rules/FAQ is a good idea to read too.

In short, Internal needs the same network name for all Guests. Then you configure them with the same range, say 192.168.100.x. Where the AD/DC and App server have static addresses. They prefer that. The W7 cilent can have DHCP, and it makes it easier to add more clients to them (plus you learn how to configure DHCP and how it works too).

[Vioxm1]

I actualy printed every page of the 280 page user manual just for this purpose. CH6 does explain everything I wanted to know, except for troubleshooting why it's not working. DHCP is turned on with ip configuration within range. It could be that my DNS is not configured correctly but I dought it. I will check the tutorials though thanks

[BillG]

Perhaps you should be reading a networking text, not the VirtualBox manual. As Sasquatch pointed out, all you have to do as far as VirtualBox is concerned is make sure that all machines are in the same internal network. This is equivalent to plugging three physical machines into the same hub/switch. From there on, you use standard networking troubleshooting if you have problems. VirtualBox is not involved.

This isn't just a guess. I have a Windows domain running in a VirtualBox internal network.