Discussion Locked

DHCP Conversion Problems

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have just recently (finally!) switched from static private IP addressing to DHCP. I have a couple of NT-Workstations that will not find domain after login but "get" a DHCP address info including my two DNS. When I switch these back to a static IP that is NOT in the DHCP range, they login just fine. Any ideas???

5 replies

by jayanth

Try adding the IP address of your PDC & BDC in the LMHOSTS file of the clients. OR you can also setup a WINS server and then try.

by nettek

If you are getting "No domain controller found..." or "No domain controller available..." messages, I have seen this before. I have never been able to find a solution other than to extend the timeout period before the workstation gives up on tryingto find the DC.

Navigate to HLM\SYSTEM\CurrentControlSet\Netlogon\Parameters
Find the ExpectedDialupDelay key. The value is in seconds. Try increasing the value. The minimum is 0, and the max is 600 (that's ten minutes! so you probably won't need to go that high)

This discussion is closed to new replies.