Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mystery IP conflicts on W2K server DHCP

Status
Not open for further replies.

andrew12

IS-IT--Management
Jun 28, 2002
56
GB
We're experiencing some ip conflicts on our network - nothing unusual there but we have two brand new W2K servers providing DHCP to nearly 300 clients on our network. The remaining clients have static ip addresses.

The clients are correctly configured and the ranges on the DHCP servers are for the most part working okay. The dhcp logs just tell us that addresses are being assigned but are then causing a conflict. The dhcp ranges are completely different from the static ranges so there are no conflicts there.

We are trying to work out whether for some reason the servers are allocating ip addresses that are already in use or if the clients are not coorectly releasing and renewing at the end of the 10 day lease period.

Any ideas?
 
You aren't using the same wire for both servers/subnets are you?
 
Both servers are on the same subnet. By wire do you mean physical cabling? If so then yes they are.
 
Erm... I think you've answered your own question:

"we have two brand new W2K servers providing DHCP to nearly 300 clients on our network"

Only one machine should be providing DHCP leases as far as I know? Or am I missing something with a 2K domain or something?
 
I'm sorry, my mistake. I should have written that although we have two DHCP servers on the same subnet one is hosting a primary scope and the other a secondary.

The two scopes do not overlap.
 
This may seam to simple, but make sure that the static ip address being used are reserved and not being assigned to by the DHCP
 
Do you have anything else that could be assigning IP's besides the servers running? I know this sounds hard to believe, but we were experimenting with wireless networking here, and our server slowed to a crawl. (We don't use dhcp.) Finally had to call in outside help as re-booting didn't help. Found out the wireless router had assigned itself the same ip as the server, even though we hard coded the router's ip. We unplugged the router, plugged it back in, and it defaulted to the ip we gave it, and the server was back to normal. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com
[americanflag]

"There is nothing like a dream to create the future."
Victor Hugo (1802-1885); French writer.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top