Jump to content

Recommended Posts

Posted

I have set up a Server 2003 VPC as a domain controller on my work pc. I also have set up a XP Pro SP2 VPC as well. I gave the Server a 192.168.1.1 static ip address. I have configured the server as a DC with DHCP and DNS. I have to give the XP Pro a static IP as well to get it to talk to the domain as it picks up our work IP range as default form the network DHCP server.

 

I thought once i joined the VPC XP box tot the Virtual Domain server, it would then pick up a DHCP from the virtual domain. But as soon as i tell the XP box to get a DHCP address it defaults back to our REAL network range which is in a 172.*.*.* range.

 

 

Is this correct, if so how can i test if my VPC servers DDHCP is working?

 

DO i need to remove the NIC cable from my test box? or add a second NIC?

Posted
I'm not too familiar with Virtual PC but in VMWare you can set the virtual NIC to be part of a 'host-only network' to achieve the desired result. This is the sort of setting I would look for. Isuspect that unplugging the patch or disabling the host's NIC would also give the desired result. You may also find that the DHCP server running in the VM may 'leak out' onto your network.
Posted
If I remember rightly this is to do with the default config, which is to bridge the virtual network rather than NAT. I would check the settings on the virtual server to make sure you have the virtual network card set to NAT or... if it has it... route, not sure as I haven't got a Virtual PC in front of me. Moved over to VMware a couple of weeks ago cause it seems a lot more responsive.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...