Discussion Locked

User Authentication Errors-Event ID 529

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

We have a couple of services on our NT 4.0 SP6a workstations that show up as logged on users when the service starts on the system (Norton AV, SMS, etc). Then when the user logs in, all accounts that are used for various services try to go out and authenticate against the user's persistent drive mappings, causing the servers that house those shares to log event ID 529 in the security log as a failed logon attempt (not all service accounts are domain admin accounts, and some users map drives toresource domains where the service accounts have no permissions). Is there a way to prevent the workstations from trying to authenticate to mapped drives with accounts used on services running, or is this just a feature that we have to live with? The users can get to the shares O.K. after logging in, I just don't like to see all the logon failures show up in our servers' security logs and would like to keep the service accounts from even trying to authenticate if possible. Thanks for the help.

Arlo McCalla
arlo.mccalla@afpc.randolph.af.mil

3 replies

by arlo mccalla

Thanks for the post, but not exactly what I was looking for. I'm just curious why the services that are logged on to the system are even trying to authenticate to the mapped drives as the user logs in, and if this can be prevented or not. For instance, the Norton Anti-Virus software we run uses a service that is set to run under a domain account, and when a user logs in, this account goes out and tries to authenticate to the users mapped drives (along with the user's account as well), causingthe Event ID 529 to trigger since the Norton account doesn't have access to that share. If this is by design, please point me to the correct source for the info. Thanks!

This discussion is closed to new replies.