Post reply

Connections

  • May 16, 2008 at 6:28 am

    #154358

    I am getting this error 'cannot generate SSPI context'

    When I connect through Remote desktop to this server I can successfully able to log in to SQL server, when I log in from my desktop I am getting this error 'cannot generate SSPI context'.

    I did connect other server from my desktop succefully and they all are in same domain. I don't know why I am geeting error for this server only.

    Please help

  • May 16, 2008 at 7:07 am

    #816449

    Hi,

    This may not be the answer but i get this sometimes with the following conditions;

    I have two physical machines that i use here in the office.

    We have expiration policies in place on passwords.

    When i am logged onto one machine, that i tend to use mostly because all of my music and old code is there, and my password expires if i do not log out of both machines then sign back in on one changing the password. The other machine will start throwing those errors.

    Do you happen to have two machines? Do you have some application running under an account with an expired password? You mentioned RDPing into another box, is that session hung and since the hanging have you changed your password (this one has also happened to me)?

    Hth,

    Brian

    Think great, be great!

  • May 16, 2008 at 7:27 am

    #816466

    No, I can remotely login to the server but I cannot access through Desktop

  • May 16, 2008 at 7:42 am

    #816479

    See if this KB article helps then http://support.microsoft.com/kb/811889

    Think great, be great!

  • May 16, 2008 at 12:24 pm

    #816672

    I guess your server does not allow remote access. Check out in your

    Connections.

  • May 16, 2008 at 1:53 pm

    #816719

    As I said I can remotely Login to server but not trhough my desktop. does it still requires remote connection?

  • May 17, 2008 at 8:54 am

    #816862

    are u gettin this error using both sql logins and windows logins, it might be domain and authentication problems, check the event log it would help.

    ..>>..

    MobashA

  • May 17, 2008 at 9:45 am

    #816876

    As asked, have you tested a remote connection form another source other than your desktop? The problem could be either at the server or at your desktop. Testing from another source will confirm where the problem is. If it works from another source, then it's your desktop. If it doesn't work, it is the server.

    If it is the server, look at the KB article cited (811889) because there are several causes to this. One could be misconfigured SPNs which prevent a Kerberos connection from working properly. And that would make sense that it would work locally but not remotely in some of those situations.

    Also, I know it was asked, but it won't help to test with a SQL Server based login. SSPI only comes into play when dealing with Windows authentication.

    K. Brian Kelley
    @kbriankelley

  • May 17, 2008 at 2:44 pm

    #816896

    yes if the problem only when using windows loggins then u might have SPN problem and u have to u fix the SPN ur self from the command line "setspn.exe".

    ..>>..

    MobashA

  • May 17, 2008 at 8:57 pm

    #816918

    I get this once in a while myself and (for me) it has always turned out to be a domain trust/authorization problem. YMMV.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

  • May 19, 2008 at 8:30 am

    #817199

    It does not work on my desktop or any other computer/server.

    Thanks

    Nita

  • May 19, 2008 at 8:31 am

    #817200

    So how did you resolve it?

    THanks

    Nita

  • May 19, 2008 at 9:24 am

    #817263

    Well, in my case, it only happens when my laptop has been working off-line for more than 24 hours. I can solve it by just going on-line to the domain again.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

  • May 19, 2008 at 3:06 pm

    #817467

    If the case is it's not working from any remote host, that pinpoints it as a server problem. Take a look at the KB article cited earlier, it's probably the best source to get started. There are several reasons for SSPI errors and just seeing that error message alone isn't enough to go on. You may need to get your server/directory services administrators involved.

    K. Brian Kelley
    @kbriankelley

Viewing 14 posts - 1 through 13 (of 13 total)

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