n00b networking question.

Soldato
Joined
26 Apr 2003
Posts
5,746
Location
West Midlands
I'm having issues with client computers getting the correct DNS address from the server.

In a VM enviroment I have Server 2008 RC2 as my domain controller an I have a Windows 7 Enterprise client. Now when I first come to log on to the client the machine will have the correct IP for the DNS server of 192.168.159.134 which is also the address of the Server, thats what I want. Now when I log off and few times and switch users and what not the DNS IP then changes to 192.168.159.2 which is the gateway IP which then means I can't apply any GPO or anything. I can retrieve the correct IP by relasing and renewing the IP using ipconfig. I've also tried to apply a DNS GPO so it always goes to 192.168.159.134 but it had no effect. Any ideas?

Just showing that the DHCP is set to 192.168.159.134
dhcp.png


Clients IP config.
cmdxq.png
 
Looks like you've two DHCP servers, one of which is giving out the same IP pool but a different DNS server.
 
Is the default gateway a router? Is the router also acting as a DHCP server?

I have a Virgin Media Superhub as my router in the house but these two machines are running in a virtual enviroment, would the router have anything to do with this?

Looks like you've two DHCP servers, one of which is giving out the same IP pool but a different DNS server.

Can you give any advice where I would look and check settings for this?
 
But this being in a VE surely my external rotuer would have no bearing on this? It's all emulated NIC's and made up IP's? The IP's in the VE aren't the same as what my host machine are using or the router.
 
Just 192.168.159.134 which is what I want. I think I may of sorted now. In the configuration for the server NIC I had the DNS set to 127.0.0.1 to point to itself, I changed that to 192.168.159.134.
 
Just 192.168.159.134 which is what I want. I think I may of sorted now. In the configuration for the server NIC I had the DNS set to 127.0.0.1 to point to itself, I changed that to 192.168.159.134.

It should be 127.0.0.1 if it's hosting DNS... at least in my experience anyway.
 
Ok turns out that hasn't actually worked so I've put it back to 127.0.0.1. I'm still having the same issue. =/
 
Sorry to bump this but I'm still having this issue, I've even got a ubuntu client to be added and again that is aslo picking up 192.168.159.2 as the DNS server instead of 192.168.159.134.

Just wondering if I need to change the network adapter settings in the VM software as all the VM's have the network adapters configured to NAT?
 
Correct. I'm totally at a loss. I've even assigned a GPO to set the DNS to 192.168.159.134 yet that still doesn't work.
 
Correct. I'm totally at a loss. I've even assigned a GPO to set the DNS to 192.168.159.134 yet that still doesn't work.

I still think it's something within Vmware Server. Have you completely stopped the DHCP service?

I would install wireshark on the client and go though the DHCP process line by line.
 
Back
Top Bottom