Steps to troubleshoot SQL connectivity issues

Sticky Steps to troubleshoot SQL connectivity issues

  • 2008년 4월 30일 수요일 오후 4:40
    중재자
     
     

    Please follow this blog to troubleshoot SQL connectivity issue and post question here.

    Steps to troubleshoot SQL connectivity issues

    Lot of blogs related to SQL connectivity issue are available sql_protocols blog.

    http://blogs.msdn.com/sql_protocols


    (Update: Please search your error message in this forum before you post your question, there are probably already answers in previous posts. If your scenario is different, please start a new thread rather than appending to old ones. Please reply this thread if this searching step solves your issue. We would like to hear from you. Thanks).

     

모든 응답

  • 2012년 1월 5일 목요일 오전 5:36
     
     

    Thanks for your good information.

    I followed your step to step2, the log file showed "error :9003, severity: 20, state:1".

    Could you teach me how to solve this problem or could you provide the URL for how to uninstall SQL Server 2008 and reinstall"

     

    thank you very much


    I have uninstall and reinstall the SQL Server 2008 already.

    Thanks for your read.

  • 2012년 8월 2일 목요일 오후 9:04
     
     
    The SQL Server connection tool pointed me at the problem- my connection string user and password were being ignored in favor of the windows login I happened to be using.
  • 2013년 3월 4일 월요일 오전 3:50
    중재자
     
      코드 있음

    In lieu of TELNET, one can check port connectivity with the PowerShell command below.  Specify the desired port number instead of the default instance port 1433 as needed.

    1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }


    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • 2013년 3월 16일 토요일 오후 9:51
     
     

    Xinwei Hong

    I have done the tests recommended in you post by going through the steps in "Steps to troubleshoot SQL connectivity issues" Turning off the Firewall solved the problem, but naturally, I don't want to leave it turned off.

    Here are the settings I have changed and the results:

    Firewall off: Instant connection.

    Domain Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

    Private Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

    Public Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

    All three of the above set to Allow (No Results) Time Out at 15 seconds

    IPSec Settings: All computers on the domain added to Only Allow Exceptions. (No results) Time Out at 15 seconds

    IPSec Settings: Added Domain Admins to Only Allow Authorized list.

    Are there any other firewall settings I can try resetting?



    Tom Childers, Radio Amateur N5GE, Licensed since 1976, QCWA Member 35102, ARRL Life Member