General discussion

Locked

DHCP gone ballistic

By And_the_beat_goes_on ·
my DHCP Server is deteriorating rapidly, Scenario:NT 4.0 SP6a
DHCP Scope: 10.10.1-179, 24 bit subnet.
With greater frequency, clients are being served 8 bit subnet masks. Bad_Addresses coming and going within scope. DHCPLOC tool on resource kit reveals no other DHCP server, however is OFFERing addresses but on some OFFERs an ACK is never received from any node. The address being offered shows up in DHCP Admin with no client name associated with the address. After some time must be the server stops the OFFER. Tried deleting the scope and recreating it to no avail. Any HELP would be greatly appreciated

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DHCP gone ballistic

by Deming Schools Network In reply to DHCP gone ballistic

Assuming this is the only DHCP server on your network and you are not subnetting... I would remove the DHCP Service and re-install from the NT CD... then re-apply your Service Pack 6a. This will require you to reboot your server, so if it is running an application everyone is using, make sure you get them to disconnect first.

Good Luck!

Collapse -

DHCP gone ballistic

by And_the_beat_goes_on In reply to DHCP gone ballistic

Poster rated this answer

Collapse -

DHCP gone ballistic

by Paul D. Masley In reply to DHCP gone ballistic

I do not believe that you are having problems with your DHCP package, but this sounds like you may have several NICS that has either took a voltage surge or lightning hit. Usually when specs show that only 16 or 8 bit masks are accepted, the clientNICS are at fault. I would not pass checking the NIC(s) in the server and also check any routers, bridges ect. I have found that a shorted cable will also cause this problem. You are in for a hunt. Good Hunting.

Collapse -

DHCP gone ballistic

by And_the_beat_goes_on In reply to DHCP gone ballistic

Poster rated this answer

Collapse -

DHCP gone ballistic

by Frobo In reply to DHCP gone ballistic

I agree with answer two, you looked in the wrong place. It seems that this not a kind of NT-DHCP Problem. You had to look deeper on the NIC and cable aso.


regards

Frobo

Collapse -

DHCP gone ballistic

by And_the_beat_goes_on In reply to DHCP gone ballistic

Poster rated this answer

Collapse -

DHCP gone ballistic

by BudgieSoft In reply to DHCP gone ballistic

Use a sniffer and watch one of the nodes that's not ACKing. Release and renew the address for the node several times.

If the ACKs are being sent but not displayed, immediately compress the DHCP database. The process for compressing it is similar to the one you are using to keep your WINS database compressed.

Collapse -

DHCP gone ballistic

by And_the_beat_goes_on In reply to DHCP gone ballistic

Poster rated this answer

Collapse -

DHCP gone ballistic

by And_the_beat_goes_on In reply to DHCP gone ballistic

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums