SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'


Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Author
Message
NewBornDBA2017
NewBornDBA2017
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3832 Visits: 924
One of the user who has DB owner rights on the database(dbs-sqlprod4), trying to access one of the view from the linked servers (dbs-sqlprod5) gets this error. If he runs it when is on prod4, then it works just fine.
However, I don't run into any issues since I have SA rights on prod4.

Select * from [dbs-sqlprod4].Farmreach.dm.ProfarmerNewsletter
Where FJID in
( 4147071000)
Msg 18456, Level 14, State 1, Line 13

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Sue_H
Sue_H
SSC Guru
SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)

Group: General Forum Members
Points: 72536 Visits: 14916
NewBornDBA2017 - Tuesday, December 19, 2017 9:43 AM
One of the user who has DB owner rights on the database(dbs-sqlprod4), trying to access one of the view from the linked servers (dbs-sqlprod5) gets this error. If he runs it when is on prod4, then it works just fine.
However, I don't run into any issues since I have SA rights on prod4.

Select * from [dbs-sqlprod4].Farmreach.dm.ProfarmerNewsletter
Where FJID in
( 4147071000)
Msg 18456, Level 14, State 1, Line 13

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.


You get that error when no credentials are passed to the other server. What is setup for the login mappings for the linked server?

Sue



Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)SSC Guru (212K reputation)

Group: General Forum Members
Points: 212822 Visits: 18586
NewBornDBA2017 - Tuesday, December 19, 2017 9:43 AM
One of the user who has DB owner rights on the database(dbs-sqlprod4), trying to access one of the view from the linked servers (dbs-sqlprod5) gets this error. If he runs it when is on prod4, then it works just fine.
However, I don't run into any issues since I have SA rights on prod4.

Select * from [dbs-sqlprod4].Farmreach.dm.ProfarmerNewsletter
Where FJID in
( 4147071000)
Msg 18456, Level 14, State 1, Line 13

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Check the SPNs are registered and registered correctly for the instances


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
NewBornDBA2017
NewBornDBA2017
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3832 Visits: 924
He was logged into his own computer so his personal windows credentials were getting passed (laptop-hfgdjhg/ssmith) so no wonder he was getting that error.
I asked him to make RDP conenction and he didn't have any issues once he was logged on to the server using his domain acct.
anthony.green
anthony.green
SSC Guru
SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)SSC Guru (101K reputation)

Group: General Forum Members
Points: 101334 Visits: 8698
NewBornDBA2017 - Wednesday, December 20, 2017 9:17 AM
He was logged into his own computer so his personal windows credentials were getting passed (laptop-hfgdjhg/ssmith) so no wonder he was getting that error.
I asked him to make RDP conenction and he didn't have any issues once he was logged on to the server using his domain acct.


So you had the triple hop error, as Perry detailed for that fix you need to get the SPN's setup correctly to allow Kerberos to pass the tokens through the multiple machines.

Me being paranoid I would look at fixing that than RDP rights as I like to lock down those rights to privileged people only.



How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger


Sue_H
Sue_H
SSC Guru
SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)

Group: General Forum Members
Points: 72536 Visits: 14916
NewBornDBA2017 - Wednesday, December 20, 2017 9:17 AM
He was logged into his own computer so his personal windows credentials were getting passed (laptop-hfgdjhg/ssmith) so no wonder he was getting that error.
I asked him to make RDP conenction and he didn't have any issues once he was logged on to the server using his domain acct.


So when it worked for you and you had no issues, you must have been using a SQL login.

Sue



NewBornDBA2017
NewBornDBA2017
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3832 Visits: 924
Sue_H - Wednesday, December 20, 2017 10:36 AM
So when it worked for you and you had no issues, you must have been using a SQL login.

Sue

SQL Login? what makes you say that? I was using Windows authentication.
Also, I just want to make sure that there is no confusion. We used to have an employee who would use SSMS to login, now he is no longer working for us but does some consulting work for the company. He doesn't have company's laptop anymore so he is asking if his machine name ( 'LAPTOP-AJ0F871P\greg’) can be added into the company's AD so he can use his personal laptop to access our DBs using windows authentication. Is that even possible?

Sue_H
Sue_H
SSC Guru
SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)SSC Guru (72K reputation)

Group: General Forum Members
Points: 72536 Visits: 14916
NewBornDBA2017 - Wednesday, December 20, 2017 11:27 AM
Sue_H - Wednesday, December 20, 2017 10:36 AM
So when it worked for you and you had no issues, you must have been using a SQL login.

Sue

SQL Login? what makes you say that? I was using Windows authentication.
Also, I just want to make sure that there is no confusion. We used to have an employee who would use SSMS to login, now he is no longer working for us but does some consulting work for the company. He doesn't have company's laptop anymore so he is asking if his machine name ( 'LAPTOP-AJ0F871P\greg’) can be added into the company's AD so he can use his personal laptop to access our DBs using windows authentication. Is that even possible?


Because if it's an issue of SPNs for the service account, you would have had the double hop issue as well.
That's why I was asking about the security mapping because you had reported you had no errors and it worked fine. The other non-sysadmin user had the issues.

Sue



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search