(SOLVED) Finalizing VM Network

[JRaff]

This is most likely a combination of windows networking and VM question but hopefully someone will be able to help.

Machines Involved:

Host:
Win7 64-bit SP1
AMD A8-3500M w/ Radeon HD 1.5GHz
6GB RAM

Guest 1:
Win server 2003
1 CPU
1024 MB RAM
Vid 128 MB w/ 3D accel
Net Adapter: PCnet-FAST III (Internal network, 'Pen Test Lab')

Guests 2 & 3:
Win XP Pro SP3
1 CPU
1024 MB RAM
Vid 128 MB w/ 3D accel
Net Adapter: Net Adapter: PCnet-FAST III (Internal network, 'Pen Test Lab')

Here's where I am at...

The 2k3 machine is running as DC, DNS Server, and DHCP Server. I have AD domain setup as "pentestlab. training. com" and both XP machines have joined the domain no problems. Users and passwords are good and the machines are getting IP addresses from DHCP from the pool I set up (10.10.10.10-10.10.10.15)

All 3 machines can ping each other by IP address no problems. When I try to ping the domain "pentestlab. training. com" I get "Ping request could not find host "pentestlab. training. com". Please check the name and try again."

None of the machines can access the internet right now. I understand that I need to set up a 4th machine to handle that, if I have read all the manuals correctly, and that's where my problem lies. How do I set up the 4th machine to handle internet connectivity for the existing 3? Once that issue gets resolved will it also resolve the problem pinging the domain?

[BillG]

It really has nothing to do with VirtualBox from here on. The setup of a domain on its own network is just the same whether you use virtual or physical machines and networks. It you want to give the machines Internet access you need a router (an not on the DC). The DC should not be multihomed. Give the DC just one NIC like the clients and set up a vm as a NAT router (to route between the internal network and the physical network).

The client machines should use the DC ONLY for DNS. Modify the DNS on the DC to forward to a public DNS to resolve URLs for its clients. Do not put additional DNS addresses on the clients, not even as secondaries.

[FrodoHobbits]

Take a look at this tutorial. It will help you setup a PFsense router and it doesn't use up to much in resources either.
http://www.slideshare.net/rpainter/how- ... virtualbox

[JRaff]

Take a look at this tutorial. It will help you setup a PFsense router and it doesn't use up to much in resources either.
http://www.slideshare.net/rpainter/how- ... virtualbox

Thanks for that link. It solved all my problems and everything works like a champ!!! I knew it was going to be as easy fix and I realized I had downloaded the wrong .iso file for pfsense. I was trying to load the amd64 version and it kept getting hung up on the install.

Thanks again....now that I've got it up and running it's time to learn how to hack it haha