Networks

Ask something
Discussion Locked

Active Directory Problems

0 helpful
3 replies

by el sombre

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

About 3 months ago we upgraded our two servers to AD. All client workstations (mixed 98/NT/Win2K) were able to logon to the Domain perfectly for about 2 weeks. Then, one at a time (over a period of about 12 weeks), all Win2K clients would lose connection with the network and could not regain access to the Domain. We only have 1 remaining Win2K client with access to the Domain.

By changing the network settings of the "dropped" clients to look for the "workgroup" with the same name as the Domain we are able to still gain access to the PDC (with all appropriate rights!) but the Domain cannot be found and no authorization is possible.

This limitation does not exist with the Win9x or NT clients - only the Win2K clients. We have staticIP addresses for all nodes.

3 replies

by jose_12650

Are they able to log on to the domain the first time the machines are booted and then forced to log-off later? If so, try typing net start from the run command on the logged-off computer. Try configuring the NIC of the clients for auto-negotiation instead of full-duplexing.

Did you examine the log on system (event viewer) from the server to determine if this error has been logged and for what reason?

by el sombre

Thanks but I closed the question about 2 weeks ago when I found out that I needed to create an lmhost file because of the DNS service running on the PDC.

This discussion is closed to new replies.