S
Stephanie
I have 2 DC's running ADS & DNS. DC1 is older 266 running primary DNS.
DC2 is newer 1.4 running secondary DNS. In the last couple of months I
have encountered this strange problem 3 or 4 times. The only solution
found so far is to reboot DC2. Both are handling authentication up
until the point of ADS hanging. At that point no one can log in -
neither DC is authenticating. Both servers are up and running and no
errors are reported in event logs on servers. But refreshing objects
in ADS Users & Computers comes up empty if it is already open (if it
isn't open on DC2 - it never opens - mmc hangs). Rebooting DC2 seems
to correct the problem. Even before DC2 is back up DC1 is
authenticating again.
Event log errors on workstations (not all showing on all workstations)
around this time include
1053 - Cannot determine computername; LsaSrv 40961 - cannot establish
secure connection with logon server, no authentication protocal is
available; 5719 - no DC available, no RPC server available
Any ideas as to what is causing this? Any other solutions other than
rebooting DC2?
DC2 is newer 1.4 running secondary DNS. In the last couple of months I
have encountered this strange problem 3 or 4 times. The only solution
found so far is to reboot DC2. Both are handling authentication up
until the point of ADS hanging. At that point no one can log in -
neither DC is authenticating. Both servers are up and running and no
errors are reported in event logs on servers. But refreshing objects
in ADS Users & Computers comes up empty if it is already open (if it
isn't open on DC2 - it never opens - mmc hangs). Rebooting DC2 seems
to correct the problem. Even before DC2 is back up DC1 is
authenticating again.
Event log errors on workstations (not all showing on all workstations)
around this time include
1053 - Cannot determine computername; LsaSrv 40961 - cannot establish
secure connection with logon server, no authentication protocal is
available; 5719 - no DC available, no RPC server available
Any ideas as to what is causing this? Any other solutions other than
rebooting DC2?