Guideline for Connectivity Question Posting


  • This was originally posted on


    In order to better assist troubleshooting connectivity related issue, the more specific the problem you describe, the faster we can help you out. Please take a few minutes to answer the following questions and post the answers as much as possible along with your specific repro steps.

  may already have your question answered. Check it out.


    [1] Client side:

    1. What is the connection string in you app? (please specify)
    2. If client fails to connect, what is the client error messages? (please specify)
    3. Is the client remote or local to the SQL server machine? [Remote | Local]
    4. Can you ping your server? [YES | NO ]

    In cmd.exe console, type “ping -a <server_name>”.

    1. Can you telnet to your SQL Server? [YES | NO, please specify the error message ]

    In cmd.exe console, type “telnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+’[‘ to bring up telnet prompt and type “quit” <enter>.

    1. What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] Or/And, what is your client application? [SQL Management Studio | SQL Profiler | Visual Studio | Other (please specify).
    2. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup)
    3. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes].
    4. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias.
    5. Do you select force encryption on server and/or client?


    [2] Server side:


    1. What is the MS SQL version? [ SQL Server 2005 | SQL Sever 2005 ]
    2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)].
    3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm.
    4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG?
    5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO]
    6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account]
    7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable]
    8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable ]


    [3] Platform:

    1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ].
    2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify)].


    [4] Misc:

    1. If you have certificate configuration issue: Please use “certutil.exe –v –store my” to dump certificate specific info and post it in your question.


    1. Find SQL Server Errorlog: Default to C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG


    Last but not least:

    There is a wealth of information already available to help you answer your questions.


    (1) SQL Server 2005 Books Online:

    (2) Microsoft Support Knowledge Base:

    (3) SQL Protocol Team Blog:

    (4) MSN Search: or use your favorite search engine.


    2006年11月30日 23:01