Windows Server 2003 and Windows XP as guests?

[gtg]

Hello,

I was wondering if it's possible to simulate a working server/client relationship using virtualbox? Basically, what I want to happen is to install windows server 2003 as a guest and then create another guest w/ windows xp. I want that xp computer to be able to talk to the server 2003 guest, i.e., to create a domain and allow xp computer to retrieve and send files.

thanks,

[vbox4me2]

Easely done via Bridge mode.

[FrodoHobbits]

I created a similar setup using the internal network option and the domain worked a treat

[BillG]

Yep, internal is the best bet if you want to install a domain controller. A domain works best in its own network on its own IP subnet.

[gtg]

Would these be the correct steps:

Set these network adapter for this as bridge?

Machine 1:

1. After completing the win2003 install
2. start-> run -> dcpromo
3. select -> D.C. for a new domain ->Domain in a new forest
4. Full dns name = test1.local
5. Domain netbios name = test1
6. Then leave everything as default till it finishes.

Need to configure the ip
7. IP address = 192.168.1.8
subnet mask = 255.255.255.0
default gateway = 192.168.1.1

preferred dns = 127.0.0.1

Then wait for everything to finish.

Now we start a new Machine #2 that has windows xp.

Do I then set the network adapter as bridge also for this machine?

Once computer has windows xp installed, I right click on my computer -> change the computer name and add it to the test1 domain?

Is that how the process should go?

Conversely, should I be able to ping machine 1 when i'm on machine 2?

thanks,

[BillG]

Give the server a static IP before you run dcpromo. Accept the option for dcpromo to set up DNS for you.

I would run this on an internal network, not bridged. You can then run DHCP in the internal network to automatically configure the domain clients. AD clients must use the local DNS running on the DC for AD to run successfully. This really has nothing to do with VirtualBox. It's how AD works. It uses DNS to find AD resources including the netlogon server.

[poonamji]

Ok i'm keen on knowing how to get this working too and I'm also dead stuck. I want a virtualbox Windows 2003 server to talk to a virtualbox XP professional all sitting on Arch Linux. I'm a bit of a noob so it's a little tricky.

I think what everyone is saying is that in the virtual box settings go to network and change the adapter to a bridged adapter or an internal network adapter. Beyond there i'm having difficulties too. My 2003 server can't ping anything.

Has a guide on this been written anywhere?

[BillG]

There are lots of guides on how to set up AD. The fact that you are running virtual machines really doesn't change what you need to do.

With physical machines and a physical network you would plug the server into a switch. You would install the OS in the server, give it a static IP in its own IP subnet and run dcpromo. You would then plug the client machine into the switch and install its OS. Whether you configure its networking manually or use DHCP on the server is your choice.

If you connect both of your vms to the internal virtual network it works just like the scenario above.

[gtg]

Give the server a static IP before you run dcpromo. Accept the option for dcpromo to set up DNS for you.

I would run this on an internal network, not bridged. You can then run DHCP in the internal network to automatically configure the domain clients. AD clients must use the local DNS running on the DC for AD to run successfully. This really has nothing to do with VirtualBox. It's how AD works. It uses DNS to find AD resources including the netlogon server.

Thanks for the explanation Bill. I guess that only thing that I couldn't get around on is how the VM server and VM client can talk to each other....but after your explanation, it kinda makes sense.

Alright, off I go and test this out.