• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 627
  • Last Modified:

Logon Failure 529

I keep getting an 529 logon failure error in the security logs.
  Reason: Unknown user name or bad password
  User Name: Johns
  Domain: HRC-SBS
  Logon Type: 3
  Logon Process: NtLmSsp
  Authentication Package: NTLM
  Workstation Name: TEMP-GX150
  Caller User Name: -
  Caller Domain: -
  Caller Logon ID: -
  Caller Process ID: -
  Transited Services: -
  Source Network Address:
  Source Port: 0

I suspected that it was a time sync problem with the affected PC so I replaced it with a temporary that has a "clean install" of XP pro w/SP2. This morning the log shows 25 new occurences.

Please help.
  • 4
  • 2
1 Solution
And the error you get is alway from the same computer?

Found the following for you to look at.
wmpierroAuthor Commented:
Yes, always the same computer. I opened Symantec System Center and the computer does not have a domain prefix. Also, the user is able to logon to the domain normaly but when he tries to access his folders on the server he has to enter his username/password again like he is in a workgroup.
wmpierroAuthor Commented:
I read the two knowledge base articles. 811082 seems to come the closest to the problem but I don't have the means to pay Microsoft for the solution. It looks like a known issue and a hotfix is avilable.
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

This actually sounds like a failure on the GC.  Remove the user account from all the groups he belongs to and add him to them again.
Then let's see what happens.  It seems as if the domain is unable to read his Universal group membership and then he does not get authenticated correctly.  Just a though... give it a go... at least this will not take time....  

--- You only need to do this is the user account has the same problem on other computers ---

I have also had the same type of problem that stemmed from the user profile having a corruption due to a domain change.  Sometimes user profiles are damaged when imported when a user is moved (with the profile) to a new domain. (this was not the case was it?)
wmpierroAuthor Commented:
No the domain was not changed. I was actually considering deleting this user as a last resort and recreating him. Unfortunately this is the vice president of the company and he is always logged in. The original server was Windows 2000 advanced that someone before me loaded. Not a direct upgrade to SBS 2003 Premium. I had to bring in a temporary W2K standard server, promote it to a domain controller, transfer all the files and user directories over, load all the programs and have all the workstations resolve DNS and WINS to the temp server. I then took the original server down using dcpromo. It was supposed to transfer the GC to the temp server. The users and Domain policy transfered correctly. The next step was to "clean install" W2K standard on the original server, reverse the above moving everything back and demoting the temp server. All this becuase I couldn't upgrade from W2K advanced. The server was working perfectly and there were no problems in the error logs until reciently. I noticed that the latest Microsoft updates have been applied however.
wmpierroAuthor Commented:
Problem solved. I deleted the user and re-created him. Everything seems to be working properly.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now