DHCP issues

[snappydragon]

I'm running a win2000 DHCP and a freebsd server with DHCP as well, for
backup. The problem is that the win2000 server no longer answers
requests, although the service is running and no problems appear in the

event logs. Is there any way for me to check the broadcasting on this
server? Is there a setting that makes this server the primary DHCP
server? Essentially, how do I force this server to answer the DHCP
requests from the clients? Any help is appreciated.

 

[Kevin D. Goodknecht Sr. [MVP]]

I'm running a win2000 DHCP and a freebsd server with DHCP as well, for
backup. The problem is that the win2000 server no longer answers
requests, although the service is running and no problems appear in
the

event logs. Is there any way for me to check the broadcasting on this
server?

There is a tool in the Windows 2000 resource kit called DHCP Locator Tool.

Is there a setting that makes this server the primary DHCP
server?

No, the first DHCP server to respond gets the lease.

Essentially, how do I force this server to answer the DHCP
requests from the clients?

Disable the other DHCP server.

 

[Herb Martin]

I'm running a win2000 DHCP and a freebsd server with DHCP as well, for
backup. The problem is that the win2000 server no longer answers
requests, although the service is running and no problems appear in the

Things that can wrong;

1) DHCP not authorized (if you have an AD domain)
2) DHCP scope (for each subnet) not activated
3) DHCP scope exhausted (out of addresses)
4) DHCP server turned OFF

Those things above can be managed from the DHCP console (MMC).

event logs. Is there any way for me to check the broadcasting on this
server?

What broadcasting? DHCP servers don't broadcast in
general (ignoring possible authorization multicasts.)

Is there a setting that makes this server the primary DHCP
server?

No. DHCP servers are promiscuous and equal. Clients
usually select the fastest responder.

Essentially, how do I force this server to answer the DHCP
requests from the clients?

Turn off all other DHCP servers (seriously). DHCP servers
are promiscuous as are the clients.

Any help is appreciated.

Do you scopes on BSD and Windows DHCP OVERLAP AND
have appropriate EXCLUSIONS to prevent assigning duplicate
addresses?

1) Scopes on multiple DHCP servers SHOULD OVERLAP *

2) Scope MUST have exclusions to prevent the same address
being assigned by different DHCP servers

* This prevents DHCP1 from NAQ (Negative Acknowledgement)
the other server's assignment offers when the clients request the
address.