Discussion Locked

DHCP problem

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Windows 2000/DHCP problem
Well, I began to have DHCP server problems a few weeks ago. It would seem that every 2-3 days, the service would shut down with a Jetpack error. After trying to reconcile the database and rebuilding one from backup, the problem continued. Per Microsoft's suggestion, I've removed the entire contents of the DHCP folder and that seemed to have solved my problem with it shutting down. Now it became a different problem. The clients reregistered and everything was going smoothly, but now, any new clients that do not have a lease on the IP address, can't get one. Anyone renewing an IP has no problem, just not getting a new one. The server reports no errors, there are plently of available IPs and I've tried using different scopes, with no luck. In some cases, what I have noticed is that even though the client doesn't get an IP, DHCP server seems to think that it has assigned it one, however, from the wrong scope. Its almost like the client doesn't get the Ack packet from the DHCP server. Addressing clients manually works fine. Any suggestions? I'd greatly appreciate the help.

7 replies

by abubin

First of all, make sure that you have authorized all your DHCP server (but I am sure you have done so). Next try checking to see if there are any "rogue" DHCP servers. These are unauthorised dhcp servers running that are unauthorized and most probably affects pre-win2k PCs. Once that is solved, at least you know the problem is from the servers. And you can start dissecting the server(s).

by golovast

The server is authorized and it is the only DHCP server running on a Win2k network. All of my PC clients are Win2k. The nodes that are actually having a problem are Macintoshes. The error log as well as DHCP log are clean.

by lumbini

Hi,
It looks like the DHCP service is corrupted. My advice is that you reinstall the Service and DONT reconcile the database. Forget the old addresses. Create one large scope to begin with and see where it gets you. If this works then your ok.If it doesn't, then you have a serious issue which should be addressed to Microsoft.
Best Regtards,
Nigel.

by johnp

Have you changed the hub/switch that the problem workstations are on . The reason I ask is that if the hub or switch is running a tree spanning program, the DHCP server has problems passing packets through the connection.
This also makes it look like the workstations are getting ip address from an unknown source of DHCP

Hope this helps, Good Luck

johnp@western-eng.com

This discussion is closed to new replies.