locked
Connection timeout 2016 RRS feed

  • Question

  • User1510859543 posted

    We added a Windows 2016 server and SQL Server 2016 to our domain and tried testing our asp.net connection and got the error below. Where can we go to fix this?

    Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=13422; handshake=14402;

    Monday, November 7, 2016 2:22 PM

Answers

  • User-691209617 posted

    It happened due to all of reason. Can you please check below mentioned check list.

    1. Check if the SQL Server has SQL and Windows authentication enabled
    2. Check if the SQL Server Browser Service is enabled and running
    3. Check if TCP/IP connections are enabled for your SQL Server instance (default is usually disabled)
    4. Check if the server firewall allows connections to the SQL Server and SQL Server Browser
    5. Check if the database user defined in your database also exists on the new SQL Server with same login credentials
    6. Check if the database user has the according access rights on your database if you moved your database from another server to the new one
    7. And last but not least, check your application database configuration if it is really doing what you expect (this should probably go first)
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, November 7, 2016 2:34 PM

All replies

  • User-691209617 posted

    It happened due to all of reason. Can you please check below mentioned check list.

    1. Check if the SQL Server has SQL and Windows authentication enabled
    2. Check if the SQL Server Browser Service is enabled and running
    3. Check if TCP/IP connections are enabled for your SQL Server instance (default is usually disabled)
    4. Check if the server firewall allows connections to the SQL Server and SQL Server Browser
    5. Check if the database user defined in your database also exists on the new SQL Server with same login credentials
    6. Check if the database user has the according access rights on your database if you moved your database from another server to the new one
    7. And last but not least, check your application database configuration if it is really doing what you expect (this should probably go first)
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, November 7, 2016 2:34 PM
  • User-484054684 posted

    Some of the reasons could be Firewall or port configuration issues

    See this discussion http://stackoverflow.com/questions/22566795/sql-server-pre-login-handshake-acknowledgement-error 

    Default port is 1433.

    For IPV4 or IPV6 configuration, you can refer these steps: http://stackoverflow.com/questions/15488922/connection-to-sql-server-works-sometimes/15488923#15488923 

    Monday, November 7, 2016 2:38 PM
  • User1510859543 posted

    It was a firewall issue.

    Monday, November 7, 2016 2:49 PM