Post reply

Linked server failed

  • November 22, 2021 at 8:01 pm

    #3955788

    HI, Here is my issue:

     

    I have 2 SQL 2019 instances and set up 1 linkded server. It works fine in local (remote to the server), but got the error from my workstation:

    Msg 18456, Level 14, State 1, Line 28

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

    Domain administrator already setup delegation and looks OK, SQL shown

    Thanks

     

    SLuSQL1

    Attachments:
    You must be logged in to view attached files.

  • November 23, 2021 at 8:10 pm

    #3956217

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • December 4, 2021 at 9:38 am

    #3960234

    Hi, did you know what was happening? Have a similar issue.

    DerekSolutions, S,L
    www.dereksolutions.com

  • December 5, 2021 at 6:39 am

    #3960375

    Siqing LU wrote:

    HI, Here is my issue:

    I have 2 SQL 2019 instances and set up 1 linkded server. It works fine in local (remote to the server), but got the error from my workstation:

    Msg 18456, Level 14, State 1, Line 28 Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

    Domain administrator already setup delegation and looks OK, SQL shown

    Thanks

    SLuSQL1

     

    Can you share more details on how you connect from local?

  • December 23, 2021 at 12:18 am

    #3966531

    HI, the problem is on Delegation setting. The keberos sensitivity flag was set, cleared the flag and reboot the server.

     

    Thanks

  • December 23, 2021 at 3:18 am

    #3966555

    Siqing LU wrote:

    HI, Here is my issue:

    I have 2 SQL 2019 instances and set up 1 linkded server. It works fine in local (remote to the server), but got the error from my workstation:

    Msg 18456, Level 14, State 1, Line 28 Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

    Domain administrator already setup delegation and looks OK, SQL shown

    Thanks

    SLuSQL1

    That "smells" like the Kerberos Dobule-Hop security feature.  I don't remember how to overcome that except to set up a job to do the work you want (either script or stored proc) and then run the job.  You might even have to schedule the job so that it will run as the SQLAgent.

     

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply