Unable to connect to Azure SQL Server from local machine

Singh, Abhinav (External) 0

I have created a SQL Server DB and added required firewall rules. However, I am unable to connect to the DB from my local machine using any SQL Editor. For e.g., DBeaver. Though, I can connect the DB using Azure's in-built "Query Editor".

I can telnet the DB server on port 1433 from my local machine.

telnet test-db-server.database.windows.net 1433

URL:

jdbc:sqlserver://test-db-server.database.windows.net:1433;database=testDB;user=testadmin@test-db-server;password=******;encrypt=true;trustServerCertificate=false;hostNameInCertificate=.database.windows.net;loginTimeout=30;

Error:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:06dfdee7-2bb5-4bbe-aa92-a7d33b429b5a

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

1 answer

Sina Salam 12,086 Reputation points

2024-11-12T13:31:04.25+00:00
Hello Singh, Abhinav (External),

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are unable to connect to Azure SQL Server from local machine.

This could happen due to many reasons starting from your local environment, and since you can connect using Azure's in-built Query Editor and telnet to the server, the issue might be related to the configuration of your SQL Editor or network settings.

Therefore, check the following, you should be able to resolve this in no time:

Ensure that your local machine's IP address is added to the firewall rules in Azure SQL Database.

Double-check the connection string for any typos or incorrect parameters. Your connection string looks correct, but it's always good to verify.

Since you're using encrypt=true, make sure that your SQL Editor supports SSL/TLS connections. Sometimes, older versions of SQL Editors might not support the required encryption protocols.

If your SQL Server is behind a Network Security Group, ensure that the NSG rules allow outbound traffic on port 1433.

If you're behind a corporate proxy, ensure that your SQL Editor is configured to use the proxy settings.

In DBeaver, go to the connection settings and ensure that the driver properties are correctly set. Sometimes, additional properties like trustServerCertificate need to be explicitly set.

Increase the loginTimeout parameter in your connection string to see if the connection is just taking longer than expected.

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
Please sign in to rate this answer.
Singh, Abhinav (External) 0 Reputation points

2024-11-12T14:17:15.7866667+00:00

Hi Sina,

Ensure that your local machine's IP address is added to the firewall rules in Azure SQL Database. Comment: Yes, already had Public IP in the server firewall rules.

Double-check the connection string for any typos or incorrect parameters. Your connection string looks correct, but it's always good to verify. Comment: All looks correct and this is not an issue with me. None of my team members are able to connect to this Azure SQL DB.

Since you're using encrypt=true, make sure that your SQL Editor supports SSL/TLS connections. Sometimes, older versions of SQL Editors might not support the required encryption protocols. Comment: All the different editors that we are using supports supports SSL/TLS connection.

If your SQL Server is behind a Network Security Group, ensure that the NSG rules allow outbound traffic on port 1433. Comment: It is not.

If you're behind a corporate proxy, ensure that your SQL Editor is configured to use the proxy settings. Comment: It is not.

In DBeaver, go to the connection settings and ensure that the driver properties are correctly set. Sometimes, additional properties like trustServerCertificate need to be explicitly set. Comment: The property trustServerCertificate is already set to true.

Increase the loginTimeout parameter in your connection string to see if the connection is just taking longer than expected. Comment: I changed it but the error is still same.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:03d76c1d-596a-43a3-988e-77808a71abed

Regards,
Abhinav

Sina Salam 12,086 Reputation points

2024-11-12T14:57:20.68+00:00

Hello Singh, Abhinav (External),

Thank you for your feedback.

Though, if this are not personal created error. The error information is generic, indicated a failure at the network or server endpoint level. So, you will need to further troubleshoot with the following steps:

Ensure the SQL Server instance is running by checking the Azure Portal to confirm the server is online and try connecting using a different network to make sure rule out local network-specific issues.

Run nslookup <your_sql_server>.database.windows.net from the command line. Ensure the SQL Server's domain resolves correctly to its IP.

In your SQL client (e.g., DBeaver), enable debug or verbose logging to capture detailed connection attempt logs. This may provide more / additional clues for further troubleshooting.

In Azure SQL Database enforces TLS 1.2 and ensure your environment and tools are configured to use TLS 1.2. You can check this using PowerShell: [Net.ServicePointManager]::SecurityProtocol

Use sqlcmd or PowerShell to test connectivity: Test-NetConnection -ComputerName <your_sql_server>.database.windows.net -Port 1433

Should there be any outage, doubt it, but verify if there are any ongoing Azure outages affecting the region of your SQL Server by checking the Azure Status Page https://status.azure.com.

Yes, as you said, you might not be using NSGs. Sometimes redundant security configurations (like additional NSGs or Azure Private Link misconfigurations) can block access. Review your Network Setting in the Azure Portal for hidden restrictions.

NOTE: AT THIS POINT. If all the above checks don't resolve the issue:

In the Azure SQL Database firewall settings, enable the "Allow Azure Services and resources to access this server" option. This ensures that any misconfigured VNet, routing, or DNS rules within Azure are bypassed.

Recreate Firewall Rules by deleting and re-add the public IP address in the firewall to ensure the rule is correctly applied.

You might need to Switch to Private Endpoint (Optional), if you suspect issues with public connectivity, configure a Private Endpoint for your Azure SQL and try connecting through a VPN or ExpressRoute to ensure private and secure access.

Contact Azure Support by raising ticket via your Azure Portal.

Success.

Singh, Abhinav (External) 0 Reputation points

2024-11-13T07:31:58.6566667+00:00

Hi,

Thanks for all the troubleshooting steps.

I have tried each suggested step; however, none of them helped in fixing the issue. Everything looks fine, still I can't connect to the Azure SQL DB.

I tried to connect to the SQL DB using Azure Data Studio and getting below error:

System.ComponentModel.Win32Exception (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

When I tried to connect using DBeaver, getting below error:

2024-11-13 12:01:41.517 - Connect with 'XXXXX' (azure-193243535e1-1e6c3b770241c72c)

2024-11-13 12:01:41.518 - Execution context opened (XXXXX; Main; 9)

Nov 13, 2024 12:02:24 PM com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin

WARNING: ConnectionID:10 ClientConnectionId: a491ee99-22a2-4de8-84a9-05a08939a0bb Prelogin error: host xxxx.database.windows.net port 1433 Error reading prelogin response: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

2024-11-13 12:02:24.360 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

org.jkiss.dbeaver.model.exec.DBCConnectException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

I tried to check port connectivity using PortQryUI and it is showing all good.

Please advice!

Singh, Abhinav (External) 0 Reputation points

2024-11-13T07:37:35.8866667+00:00

Hi,

Thanks for suggesting all the debugging instructions. I tried each of them; however, none helped in finding the solution. All the command are working fine.

Tried to use Azure Data Studio to connect to the Azure SQL DB and getting below error:

System.ComponentModel.Win32Exception (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

Tried DBeaver SQL Editor and got below error:

2024-11-13 12:01:41.517 - Connect with 'XXXXX' (azure-193243535e1-1e6c3b770241c72c)

2024-11-13 12:01:41.518 - Execution context opened (XXXXX; Main; 9)

Nov 13, 2024 12:02:24 PM com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin

WARNING: ConnectionID:10 ClientConnectionId: a491ee99-22a2-4de8-84a9-05a08939a0bb Prelogin error: host XXXXX.database.windows.net port 1433 Error reading prelogin response: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

2024-11-13 12:02:24.360 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

org.jkiss.dbeaver.model.exec.DBCConnectException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ClientConnectionId:a491ee99-22a2-4de8-84a9-05a08939a0bb

>> Tried PortQryUI to check port connectivity and all looks good.

Please Advise!

Sina Salam 12,086 Reputation points

2024-11-13T12:59:58.1066667+00:00

Hello Singh, Abhinav (External),

Thank you for your feedback. I’m sorry to hear that you’re still experiencing issues connecting to your Azure SQL Database despite following all the troubleshooting steps.

Try to update your tools and DB.

Contacting Azure Support

If none of the above steps resolve the issue, it might be time to contact Azure Support for further assistance. When raising a support ticket, provide them with the following information:

Detailed error messages and logs from your client applications.

Results of the nslookup and Test-NetConnection commands.

Any relevant screenshots or logs from the Azure Portal.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unable to connect to Azure SQL Server from local machine

1 answer

Your answer