SQL error: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON

Some users get this error when trying to connect through 'Linked Servers'

When looking in eventviewer, I find this error:

Event 18456

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.

SQL Server 2008


Thank you for your help
Alan DalaITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Deepak ChauhanSQL Server DBACommented:
Is linked server configured with windows login
Is it configured with imporsenate.

You need to check the login which is mapped in linked server should have access on remote server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alan DalaITAuthor Commented:
Thank you for your response. Here is my setup. The confusing part is that while some users get error messages, other can access the linked server just fine.

Capture.PNG
0
Alan DalaITAuthor Commented:
I think I got a step further in the troubleshooting process. I don't get this error if I remote into the server but still get it when using SQL Management Studio on my laptop.


Thanks
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Mandeep SinghDatabase AdministratorCommented:
0
Deepak ChauhanSQL Server DBACommented:
Hi Alan

Is it resolved or issue still persist?
0
Alan DalaITAuthor Commented:
I got it fixed for now but I'm missing something about Kerberos and SPNs since that was the problem. I will open another questions related to those.

Thanks
0
Deepak ChauhanSQL Server DBACommented:
Greate! Good to know.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Alan Dala, do you still need help with this question?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

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.