question

MarceloMotaManhes-4519 avatar image
0 Votes"
MarceloMotaManhes-4519 asked OuryBa-MSFT commented

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.

Hi Team

I´m facing a problem without solution

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=543; handshake=29466; (.Net SqlClient Data Provider)

I tried all steps here
https://support.microsoft.com/en-us/sbs/topic/solving-connectivity-errors-to-sql-server-ae23c94b-b64b-5056-8b62-22e1694bb889?ui=en-US&rs=en-US&ad=US

Without a solution. It says in some part that on previous link that

I Tested, Network, Firewall, SSL (Using open ssl commands) and everything looks good.

I tested for example
Ping
Telnet
Test-NetConnection <Server_FQN> -port 1433
portqry.exe -n <Server_FQN> -p tcp -e 1433

and everything works

Is there any component that I missed?

Thanks
Marcelo

azure-sql-databaseazure-network-watcher
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MarceloMotaManhes-4519 Are you trying to connect to Azure SQL ?

Regards,
Oury

0 Votes 0 ·

Yes, I´m trying to connect to Azure SQL DB.

Thank you

0 Votes 0 ·
OuryBa-MSFT avatar image
0 Votes"
OuryBa-MSFT answered OuryBa-MSFT commented

Hi @MarceloMotaManhes-4519 Thanks for getting back
This may be due to many reasons. Please check the below steps to make sure you are not missing anything.

  1. Make sure that TCP/IP is enabled as a client protocol on the application server. For more information, see Configure client protocols. On application servers where you don't have SQL tools installed, verify that TCP/IP is enabled by running cliconfg.exe (SQL Server Client Network utility).

  2. Check the application's connection string to make sure it's configured correctly. For example, make sure that the connection string specifies the correct port (1433) and fully qualified server name. See Get connection information. Looks like you checked that already

  3. Test the connectivity between the application server and the Azure SQL Database by using SQL Server management Studio (SSMS), a UDL file, ping, or telnet. For more information, see Troubleshooting connectivity issues and Diagnostics for connectivity issues. (You also did that )

Please do also check the below document if you are not missing any steps.
https://docs.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-connectivity-issues#diagnostics

If you are still having issues. I will suggest to open a support request so we can get a closer look at your environment to better troubleshoot this.

Regards,
Oury


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MarceloMotaManhes-4519 Checking if you are still facing issue to connect to Azure SQL after the above points. Please let us know

Regards,
Oury

0 Votes 0 ·
MarceloMotaManhaes-2034 avatar image
0 Votes"
MarceloMotaManhaes-2034 answered OuryBa-MSFT commented

Thank you Very Much Oury for your inputs, the issue was solved, Basically I did all steps you recommended with success. However the problem was related to internal VPN configuration as I had some missing certificates on TLS handshake process in windows level. After VPN configuration refactory it worked.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MarceloMotaManhaes-2034 I am glad it worked. Thank you so much for letting us know.

Regards,
Oury

0 Votes 0 ·