Discussion Locked

Event ID 5722

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

On my PDC I sometimes get this error message in the Event Log...

"The session setup from the computer failed to authenticate. The name of the account referenced in the security database is $. The following error occurred:
Access is denied."

It isn't causing any problems for end-users, but its irritating me to no end. :)
I perused TechNet and narrowed it down to an issue with enumeration of the SAM database and an occasional miss. We have "lost" two bdc's from the domain due to upgrade to Windows2000, which may or may not be contributing to the errors.

If anyone has seen this error and has conquered it tell me your solution!

TIA,

Bobby

5 replies

by arlo mccalla

We get this error when a workstation loses it's trust with the domain, most noticably when we reload NT using Drive Image. When the system boots up, we have it set to our domain but the trust fails, and this event is logged. What we do is change the client system to a workgroup, then add it back to the domain. This occurs about once a month on random systems already deployed as well, the trust will fail and require us to go remove and add it back to the domain. If your users aren't experiencing problems on the machine numbers being logged, this might not be the case, but may be worth a shot to try removing/adding one of the systems being logged back to the domain to see if it clears it up. Hope this helps you.

Arlo

by tdemanmsmvp

Hi.

When a NT server or NT Workstation is member of the domain, a Secure channel is maintained between the station and the NT domain database.
Each one must know the last key use by the other to authenticate it.
The station memorizes a "password" or key to give to the domain, and the domain memorizes a key in the same way. This key changes at each authentication.

If a station is not seen during too much time by the domain, the secure channel is closed. If you load an image from GHOST orPQDI, the secure channel will be probably closed or unsequenced.

2 basics solutions:
-> Use NETDOM NT Reskit to RESET the secured channel (this can be automatized for stations that monthly outside).
This simplify the procedure to extract the Workstation from domain, and ReEnter it after.

-> Delete the automatic and necessary update for the secure channel.
The variable "DisablePasswordChange" in the NETLOGON service Key.
Take in account that this can be a lower security.
NB: Look at Reskit guides for more informations (and perhaps others key to change).

=> I already used this system for remote workstation connected by low WANs.

Hoping to have helped you.
Bye.

This discussion is closed to new replies.