SQL Server 2005 connection problems

  • We have SQL server 2005 standard edition running on sql box. When I connect to server thru sql server management studio, I connect sometime and some time I cannot connect. Same connection problems is happening to aother team members. I checked the error log it says

    "SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed"

    The connection problem is not consistent. Using both tcpip and named pipes on server and client connection.

    Any idea? PLease !

  • Try following the steps in this article

    http://www.microsoft.com/technet/pro.../tkerberr.mspx

    It has instructions on how to identify the problem and how to fix it.

    CodeMinkey

  • We are having the same problem.

    http://www.microsoft.com/technet/pro.../tkerberr.mspx

    this link doesn't work!!

  • Kevin, Could you please please copy the link again, one in previuos post is not working. Thanks. Sean

  • I don't find how to resolve the connectivity error I posted in above link. Any help please, Anyone thanks.

    Kevin Can you help please to be more specific for the link and how to resolve the error. Greatly Appreciated!!!

  • 1.) Mention the servername in a fully-qualified domain name (FQDN) format or use ip address.

    2.) Try changing the protocols, its better to use TCP/IP port.

    Try connect using [servername,portnumber]

    in example: [SqlSRV1,1183]

    (Don't select 'dynamically determine port' in 'Client Network Utility>Alias' )

  • Sean (1/8/2008)


    Kevin, Could you please please copy the link again, one in previuos post is not working. Thanks. Sean

    Now how did that happen in any case here it is again

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

    CodeMinkey

  • KevinBrenn (1/8/2008)


    Sean (1/8/2008)


    Kevin, Could you please please copy the link again, one in previous post is not working. Thanks. Sean

    Now how did that happen in any case here it is again

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

    Sorry I should have explained that 0x80090311 error refers to "No authority could be contacted for authentication" which means the user cannot contact AD to get a ticket. I suggest turning on Kerberos logging and using Netmon to trace the authentication routes. You can find detailed info on how to troubleshoot Kerberos in the link (now complete that I provided)

    CodeMinkey

  • Thanks. Appreciated!!! Kevin

  • Hi Kevin or any one who is reading and following this post.

    My network admin wanted more specifics to work on problem you described in link about authentication - AD - kerberos logging.

    Problem: Using sql server management studio I sometime and my team members can connecto to SQl server and cannot connect most of time. If connected it disconnects in the middle of work. The error log is in first post. SQL server 2005 standard issue

    The problem is not related to protocols TCP and named pipes.

    I HAVE A LOT OF WORK DEPENDENT ON THE SQL SERVER AND ALL IS ON HOLD BECAUSE OF CONNECTION PROBLEMS.

    Please Help it would be greatly appreciated!!!!! Thanks in advance for you help!!1

  • Hi Kevin or any one who is reading and following this post.

    My network admin wanted more specifics to work on problem you described in link about authentication - AD - kerberos logging.

    Problem: Using sql server management studio I sometime and my team members can connecto to SQl server and cannot connect most of time. If connected it disconnects in the middle of work. The error log is in first post. SQL server 2005 standard issue

    The problem is not related to protocols TCP and named pipes.

    I HAVE A LOT OF WORK DEPENDENT ON THE SQL SERVER AND ALL IS ON HOLD BECAUSE OF CONNECTION PROBLEMS.

    Please Help it would be greatly appreciated!!!!! Thanks in advance for you help!!1

Viewing 12 posts - 1 through 11 (of 11 total)

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