locked
"Cannot generate SSPI context..." when logging into SQL RRS feed

  • Question

  • Hi All,

    I know there have been several threads on this but i think i have a unique case. I'm pretty knowledgeable in how to set up KERBEROS for SQL (have had to do it twice in the past)..but this situation is getting me stumped.

    UserA

    - can connect to ServerA using windows login

    UserB

    - cannot connect to ServerA using windows login

    Details:

    - user B, can't connect using hostname

    - user B, can connect via IP

    - user A and user B have same 'ipconfig /all' settings (DHCP server, DNS server the same, DNS suffix search order the same)

    - user B can PING server using hostname

     

    And here's the kicker. I asked User B to come to my (User A) machine and logon and try to connect to Server A. I was 99% certain she could connect, because i suspected it had to do with her desktop. But when she tried to logon to Server A using my desktop, she receied the 'SSPI' error???

    Does this mean it has something to do with her domain account? Any ideas/tips would be appreciated.

    Thanks in advance

    Monday, March 14, 2011 7:32 PM

Answers

  • As Uri mentioned, there are many information on internet for this error.
    One of them is http://support.microsoft.com/kb/811889 (How to troubleshoot the "Cannot generate SSPI context" error message)
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog: http://blogs.msdn.com/blakhani
    Team Blog: http://blogs.msdn.com/sqlserverfaq
    • Proposed as answer by WeiLin Qiao Sunday, March 20, 2011 6:37 AM
    • Marked as answer by WeiLin Qiao Wednesday, March 23, 2011 4:54 AM
    Tuesday, March 15, 2011 9:19 AM
  • Can you try connecting the server in following fashion NP:SERVERNAME . You can even add the alias for the server that you are connecting to. When you perform this task, you are also explicitly defining the protocol 

    Please refer the link provided by Balmukund Lakhani


    ------------------------------
    Thanks,Suhas V 

    • Proposed as answer by WeiLin Qiao Sunday, March 20, 2011 6:37 AM
    • Marked as answer by WeiLin Qiao Wednesday, March 23, 2011 4:54 AM
    Wednesday, March 16, 2011 6:51 AM

All replies

  • There are lots of info on the internet for the subject, once we have solved the problem that is because of clock difference between server and client
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
    Tuesday, March 15, 2011 8:58 AM
  • As Uri mentioned, there are many information on internet for this error.
    One of them is http://support.microsoft.com/kb/811889 (How to troubleshoot the "Cannot generate SSPI context" error message)
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog: http://blogs.msdn.com/blakhani
    Team Blog: http://blogs.msdn.com/sqlserverfaq
    • Proposed as answer by WeiLin Qiao Sunday, March 20, 2011 6:37 AM
    • Marked as answer by WeiLin Qiao Wednesday, March 23, 2011 4:54 AM
    Tuesday, March 15, 2011 9:19 AM
  • There are lots of info on the internet for the subject, once we have solved the problem that is because of clock difference between server and client
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/


    Yep unfortunately on my client i can connect and she can't, so that would eliminate a client issue i believe.

    Everyone else that we've tested with from their own client can connect with no problem. She can only connect via IP not hostname using her domain account. Everyone else can connect using hostname

    She can even connect to another server on the same domain using hostname and that's fine..

    ....i'm at a loss at the moment....

    Tuesday, March 15, 2011 8:52 PM


  • There are lots of info on the internet for the subject, once we have solved the problem that is because of clock difference between server and client
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/


    Yep unfortunately on my client i can connect and she can't, so that would eliminate a client issue i believe.

    Everyone else that we've tested with from their own client can connect with no problem. She can only connect via IP not hostname using her domain account. Everyone else can connect using hostname

    She can even connect to another server on the same domain using hostname and that's fine..

    ....i'm at a loss at the moment....

    connecting use SSMS? SQLCMD? remember that default protocal is Named Pipe...

    If you think my suggestion is useful, please rate it as helpful.
    If it has helped you to resolve the problem, please Mark it as Answer.

    Sevengiants.com
    Tuesday, March 15, 2011 9:21 PM
  • Can you try connecting the server in following fashion NP:SERVERNAME . You can even add the alias for the server that you are connecting to. When you perform this task, you are also explicitly defining the protocol 

    Please refer the link provided by Balmukund Lakhani


    ------------------------------
    Thanks,Suhas V 

    • Proposed as answer by WeiLin Qiao Sunday, March 20, 2011 6:37 AM
    • Marked as answer by WeiLin Qiao Wednesday, March 23, 2011 4:54 AM
    Wednesday, March 16, 2011 6:51 AM