Link to home
Start Free TrialLog in
Avatar of SteveAtLSC
SteveAtLSC

asked on

DHCP giving out wrong IP addresses

Hi, all!  running mixed Win 2k8 & Win2k3 (both R2) servers in AD domain.  DHCP servers in question on subnet are Win2k8 (one) and Win2k3 (one).

Odd problem.  All workstations on the network are config'd to get IP addy info from one of two DHCP servers running on the network; one server has one scope, the second has a different scope.  Both are configured with the same routing and DNS server IP addresses.  DNS servers config'd in DHCP are set for x.y.y.251 and x.y.z.51 (yes, two different subnets, no routing issues between offices).

When users log into network, the DNS settings they are getting from DHCP are set for x.y.y.252 and x.y.y.253.  These were our OLD DNS servers, changed weeks ago.  Caches flushes on test workstations and DNS & DHCP servers.  On one workstation I flushes the cache, released the lease (ipconfig /release), powered the machine off, and logged back on again.  The DNS settings were for the wrong y.252 and y.253 addresses.

I'm a little lost here; any suggestions?  I have verified that there are only two DHCP servers running on this subnet (x.y.y subnet).

Thanks!
SteveB
Avatar of Hypercat (Deb)
Hypercat (Deb)
Flag of United States of America image

After the workstation gets the lease, if you run ipconfig /all, what DHCP server do you see listed in the properties?
ASKER CERTIFIED SOLUTION
Avatar of SteveAtLSC
SteveAtLSC

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If your DHCP clients are in the same subnet and if the 2 DHCP servers are not aware one of the other, I can't see how you would be able to predict which DHCP server answer what host (unless you have reservations). The 2 scopes would be in the same subnet too. But maybe I got something wrong in your question.
SteveB, it would be good if you posted the cause of your problem and the solution you found, just in case someone else with the same issue is searching for a solution on EE.

Thanks,

Deb
Avatar of SteveAtLSC
SteveAtLSC

ASKER

Solution found prior to community involvement.
Look at the name servers listed in domain DNS, specifically under _msdcs.domain  Make sure to remove defunct name servers from there.