Discussion Locked

DHCP on 2k server in 4.0 Domain

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am currently in the process of migrating a 4.0 domain into AD, I have 1 PDC and 1 BDC and another BDC that will be promoted as the AD DC. I also have a 2000 member server installed into the domain, it is running, wins, dns, and dhcp, however the dhcp will not authorize and therfore will acknowledge dhcp requests or send dhcp leases. Does any one know how to make the dhcp be authorized and then give dhcp leases to clients logging into domain ? TIA

9 replies

by deltree

Log in as an enterpise administrator on the member server.
Open DHCP manager. Click DHCP
Click action/Click Manage authorized servers.
Click authorize
Type in the IP address of the server. Click OK.

by map6551

have tried that, can get the dhcp server to authorize but it will not accept or give out leases.

by deltree

Maybe the member server did not successfully become a member of the W2K domain. You might try to redo the domain membership.
Make it a member of a workgroup, then make it a member of the W2K domain, then re authorize DHCP.

by map6551

The dhcp server is still in a NT 4.0 DOMAIN not a 2k domain. If it was in a 2k domain it would authorize fine. We are migrating from a 4.0 to a 2k but are not ready to have AD implemented yet. Thanks for your input

by briantruitt

In your question it says that you have dhcp on a 2000 member server. Dhcp will only run in 2000 if you have AD set up. I think that's supposed to be one of 2000's new features. Dhcp has to be run with AD so there can be rogue server detection, etc. Try putting dhcp back on the pdc or bdc until AD can be set up on the network.

This discussion is closed to new replies.