Error 10060: Configure Azure NSG for Azure DB and Azure DW Connectivity

Jonpier Veliz 0

I have created an Azure SQL server and database and am trying to connect through SQL Server Management Studio. I am not able to connect and get the following error message: TITLE: Connect to Server

ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (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.) (Microsoft SQL Server, Error: 10060)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-10060-database-engine-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

BUTTONS:

I have set a firework rule to my client IP address. I think this has something to do with port access.

I appreciate any help.

Erland Sommarskog 112.7K Reputation points MVP

2023-03-28T21:01:19.1233333+00:00

First, are you trying to connect to SQL Server running on an Azure VM, or to an instance of Azure SQL Database?

Next, we cannot really help you, if you don't share what configurations you have done. All we can say is that the error message means that you were not able to reach the SQL Server instance you tried to connect to. That could be due to firewalls - or plain misspelling.

Note, though, that if you try to connect to Azure SQL Database and your current IP address is not among the currently configured ones, SSMS will pop up a window to permit you configure the firewall.
Oury Ba-MSFT 19,501 Reputation points Microsoft Employee

2023-03-30T16:34:09.66+00:00

@Jonpier Veliz

Just checking in to see if the below answer provided by @Alberto Morillo and @Erland Sommarskog helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Alberto Morillo 34,041 Reputation points MVP

2023-03-29T02:57:39.22+00:00

If you are trying to connect from a company network make sure TCP port 1433 is not blocked. You can also try to connect outside the corporate network using a WIFI intended for guests.

Make sure Windows Firewall or other security software on your computer, or a home router do not have port 1433 blocked also.

Another possibility is that the error is caused by DNS resolution as explained here. About Error 121 please read this Stackoverflow thread. Please enable Public Network access as explained here and add your Public IP Address to the list of allowed IPs.
Please sign in to rate this answer.
Jonpier Veliz 0 Reputation points

2023-04-03T19:49:03.4066667+00:00

Outside access on port 1433 was opened for my machine, but now I get a new error when trying to connect to my SQL instance: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) (Microsoft SQL Server, Error: 121. I have tried two things: I set a greater value for the "connection time-out" property and enabled "Trust server certificate" but still doesn't work. Do you know anything else I could try?

Alberto Morillo 34,041 Reputation points MVP

2023-04-03T23:17:14.6433333+00:00

About error 121 read this StackOverflow thread.

Jonpier Veliz 0 Reputation points

2023-04-04T17:40:09.5933333+00:00

Hello Alberto, Thank you for getting back to me. I tried setting a greater value for the connection time out setting, but it still does not work. Do you have any ideas of what I could try?

Alberto Morillo 34,041 Reputation points MVP

2023-04-04T19:33:43.4966667+00:00

Please enable Public Network access as explained here and add your Public IP Address to the list of allowed IPs.

Jonpier Veliz 0 Reputation points

2023-04-04T19:46:27.27+00:00

I have done both. Do I have to create a private endpoint?

Jonpier Veliz 0 Reputation points

2023-04-04T19:47:19+00:00

I have done both. Do I have to create a private endpoint?

Alberto Morillo 34,041 Reputation points MVP

2023-04-05T12:29:17.3033333+00:00

You created the NSG to access the Azure SQL Database maybe what you need to know is virtual network rules. You don't require a NSG or a private endpoint to access Azure unless you want to secure access to the database.

Oury Ba-MSFT 19,501 Reputation points Microsoft Employee

2023-05-15T18:33:38.6433333+00:00

Jonpier Veliz

Checking in to see if the below answer provided by @Alberto Morillo helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Sign in to comment

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

Share via

Error 10060: Configure Azure NSG for Azure DB and Azure DW Connectivity

1 answer

Your answer