DHCP Authorisation.

[XPDude]

I have the following:-

2000 AD with a Root and Child Domain, with the main server resources residing in the Child Domain.

I also have a 2-way Trust to an NT 4 Domain that holds all the users NT workstations. Within the NT Domain I have a couple of 2000 Servers running DHCP Scopes.

I have added a 2000 Server to the AD that will service DHCP requests from a Wireless VLAN. After I authroized this server in AD the 2000 servers from the NT Domain fell over with a DHCP 56 error "Authorization Failure, stopped servicing". The DHCP Service then stopped on both these servers and would not restart until I hade shut down the DHCP Service on the 2000 server in the AD.

Any ideas?

Thanks
XP.

 

[luismagally]

This might be a long shot, but this is what happen to me once. While running DHCP on an NT 4 Domain, if any DHCP server in that domain detected another DHCP server not authorized in the particular NT 4 domain, the NT 4 Server DHCP will shut down and give way to the other DHCP server. Sounds wierd, but it happen. Test the DHCP on the NT 4 Domain side to see if the 2 others shut down. I might be wrong, but that is my only suggestion at this point.

 

[pbunyon]

Lous is correct about NT DHCP server. Might you enable the W2K to handle all addressing? Issues will be prevelant with more than one DHCP server handing out addresses on one network segment, unless utilizing failover or other large enterprise specific tools/software (Lucents VitalQIP, Cisco CNR).

Paul