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

VPN/RAS server Netlogon Authentication failed error

Hi all,

I am getting this error for two of my remote users on my windows VPN server.
They can tunnel in fine, and they are not aware of any issues on there side.

Just wanted to know why just those two user will create this error, and how to clean it.

Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5722
Date:            5/8/2009
Time:            9:26:03 AM
User:            N/A
Computer:      LYRA (my RAS servers)
Description:
The session setup from the computer RSD04_LT (laptop name) failed to authenticate. The name of the account referenced in the security database is RSD04_LT$.  The following error occurred:
Access is denied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0               "..À    

Thanks

nirsky
0
STSDSE
Asked:
STSDSE
1 Solution
 
marine7275Commented:
You need to recreate a new computer account. It appears to be a SID issue.
Info below pulled from:
http://help.lockergnome.com/windows2/Event-ID-5722-fails-authenticate--ftopict482541.html

The error, and subsequent 'bad behavior' are because the domain has a
new sid for the workstation, while the worstation is utilizing the old
sid. The fix is easy, however.

First, log on locally to the workstation, with the local admin
account. Then, remove the workstation from the domain by joining it
to a workgroup. The name of the workgroup doesn't matter, so long as
it removes itself from the domain. You should get a window saying
"Welcome to the xxxx workgroup!". You'll have to reboot the
workstation for the changes to take effect.

To ensure that the machine is removed from the domain, go to a
workstation or server that has the AD User and Computers snap-in.
Ensure that POS04 is not present. If it is, delete it. wait 12
minutes to ensure replication to all GC's, if you are in a large
environment.

Now, go back to the workstation, logging on as local administrator.
Join the machine back to the domain, utilizing an account that has
sufficient privileges.
0
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

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

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