I'm using VMplayer to play with a few networking concepts and can't get DNS to work on a Win 2003 server. I setup a few VMs including an XP, Windows 2000 Workstation, and a Win 2003 Enterprise Server. I used the "add roles" tool to make the server a domain controller along with DNS and DHCP.
Right now I'm just trying to get DNS to work. My home network is 192.168.1.0 and when I setup VMs with the Network adapter set to NAT it sets up the network to 192.168.152.0 with the gateway at 192.168.152.2. All the VMs work fine using this and have internet access.
When I promoted the Win2003 VM to DC it set the static IP on the VM to 192.168.0.1 with itself as the gateway. The scope in DNS is set right and the forwarder is set for "All other domains" to 192.168.152.2.
I set a static IP of 192.168.0.200 with gateway and DNS server set to 192.168.0.1 on the XP VM and can of course ping the server but can't get out anywhere with a web request. I thought this should work, when I send a request for a web site, it should go to my 2003 VM which of course can't resolve it so it should forward it to be resolved by 192.168.152.2. What am I missing?
Homemade Windows 7 box with I7 processor and 9 GB RAM hosting VMs run by VMplayer
November 22, 2010 5:38 AM
November 25, 2010 12:25 AM