Unable to connect SQL server in SSMS

Question

Unable to connect SQL server in SSMS

Vijayakumar Bangaru (Capgemini America Inc) 40 Microsoft External Staff

TITLE: Connect to Server ------------------------------

Cannot connect to cpestaging.database.windows.net.

------------------------------ 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…

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:

OK ------------------------------

Erland Sommarskog 132.9K Reputation points

2026-03-02T17:05:37.4066667+00:00

What is says. You were not able to reach the Azure SQL Server in question. There can be a number of reasons for this. For instance the name of the server may be something else than "cpestaging".

Since you don't say why you expect connection to succeed or what troubleshooting you have conducted on your own, it is about impossible to help you.
Pilladi Padma Sai Manisha 4,990 Reputation points Microsoft External Staff Moderator

2026-03-02T17:28:44.8266667+00:00

Hi Vijayakumar Bangaru (Capgemini America Inc)
Thankyou for Reaching microsoft Q&A!
The error message indicates that the client machine is unable to establish a network connection to the Azure SQL Server cpestaging.database.windows.net. Error 10060 from the TCP Provider means the connection attempt timed out because the server did not respond. This is a connectivity issue, not a SQL authentication or credential problem.

This typically occurs when the client’s public IP address is not allowed in the Azure SQL Server firewall settings, when outbound port 1433 is blocked by a corporate firewall or network security policy, when the server is configured with Public Network Access disabled and uses a Private Endpoint, or when there is a VPN or proxy routing issue preventing traffic from reaching Azure.

To resolve this, verify that your current public IP address is added under the SQL Server’s Networking > Firewall rules in the Azure portal. Ensure that outbound TCP port 1433 is allowed from your network. If the server uses a Private Endpoint, confirm that you are connected to the appropriate virtual network. You can also test connectivity using tools such as telnet to confirm whether port 1433 is reachable.

the issue is caused by network-level connectivity restrictions preventing access to the Azure SQL endpoint, and reviewing firewall and network configuration should resolve the problem.
Pilladi Padma Sai Manisha 4,990 Reputation points Microsoft External Staff Moderator

2026-03-03T20:23:59.96+00:00

Hi Vijayakumar Bangaru (Capgemini America Inc),
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

1 answer

Your answer

Erland Sommarskog 132.9K Reputation points

2026-03-02T17:05:37.4066667+00:00

What is says. You were not able to reach the Azure SQL Server in question. There can be a number of reasons for this. For instance the name of the server may be something else than "cpestaging".

Since you don't say why you expect connection to succeed or what troubleshooting you have conducted on your own, it is about impossible to help you.
Pilladi Padma Sai Manisha 4,990 Reputation points Microsoft External Staff Moderator

2026-03-02T17:28:44.8266667+00:00

Hi Vijayakumar Bangaru (Capgemini America Inc)
Thankyou for Reaching microsoft Q&A!
The error message indicates that the client machine is unable to establish a network connection to the Azure SQL Server cpestaging.database.windows.net. Error 10060 from the TCP Provider means the connection attempt timed out because the server did not respond. This is a connectivity issue, not a SQL authentication or credential problem.

This typically occurs when the client’s public IP address is not allowed in the Azure SQL Server firewall settings, when outbound port 1433 is blocked by a corporate firewall or network security policy, when the server is configured with Public Network Access disabled and uses a Private Endpoint, or when there is a VPN or proxy routing issue preventing traffic from reaching Azure.

To resolve this, verify that your current public IP address is added under the SQL Server’s Networking > Firewall rules in the Azure portal. Ensure that outbound TCP port 1433 is allowed from your network. If the server uses a Private Endpoint, confirm that you are connected to the appropriate virtual network. You can also test connectivity using tools such as telnet to confirm whether port 1433 is reachable.

the issue is caused by network-level connectivity restrictions preventing access to the Azure SQL endpoint, and reviewing firewall and network configuration should resolve the problem.
Pilladi Padma Sai Manisha 4,990 Reputation points Microsoft External Staff Moderator

2026-03-03T20:23:59.96+00:00

Hi Vijayakumar Bangaru (Capgemini America Inc),
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Answer 1

Most of the times is a DNS resolution issue. Download and run this PowerShell script from GiHub, it will provide a diagnostic after some tests it performs.

In addition to the tool, 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 do not have port 1433 blocked also. Add your client IP address on the list of trusted IP addresses on Azure SQL firewall.

Finally, examine Resource Health on the Azure Portal because the error may be related to an incident or in-progress planned maintenance.

User's image

Share via

Unable to connect SQL server in SSMS

1 answer

Your answer