Connection error when tried to connect Azure Database from On-prem virtual machine through SQL management studio

Question

Connection error when tried to connect Azure Database from On-prem virtual machine through SQL management studio

saurabh patel 0

We're currently facing a connectivity issue while attempting to connect to the Azure database from our on-prem Virtual Machine (VM) through SQL Management Studio.Vm is hosted on ESXI. The VM consistently displays a network error message upon connection attempts. However, when we try the same connection from a physical server, it establishes successfully. In addition, we've tested this connection from two other Virtual Machines, and unfortunately, they also encountered the same error. Although we've ensured that Port 1433 is open on the VMs, we're perplexed as to why this issue persists exclusively within the VM environment despite our efforts. please share your idea if you had similar issues in past

Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-12T17:15:43.3933333+00:00

@saurabh patel
Thank you for reaching out. Could you please share the error message you are getting. Regards, Oury
Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-16T20:15:42.74+00:00

@saurabh patel Just so I understand the problem - You have one VM that is unable to reach Azure Sql Database, while other VMs on the same host can reach it fine. Is that correct? If that is the case, then please run the client side data collector and check if flags any issues?
saurabh patel 0 Reputation points

2024-01-16T20:52:18.3233333+00:00

Hey, we're experiencing connection issues on all VMs, but oddly enough, we can connect to the same Azure database from a physical machine. Both VMs and the physical machine are connected to the same firewall. Any idea what's going on? Here's the error message: TITLE: Connect to Server

Cannot connect to tcp:name.database.windows.net,1433.

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: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

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

saurabh patel 0


Hey, we're experiencing connection issues on all VMs, but oddly enough, we can connect to the same Azure database from a physical machine. Both VMs and the physical machine are connected to the same firewall. Any idea what's going on? 

Here's the error message: TITLE: Connect to Server

  Cannot connect to tcp:

name.database.windows.net,1433.  
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: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476  
  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

Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-16T21:45:51.7733333+00:00

@saurabh patel
Thank you for sharing the above details.

The above error message usually indicates a client-side networking issue, which you need to pursue from the client side. The most likely causes are the client platform being too slow to respond to the login traffic, or a problem with the network that misroutes or drops part of the network traffic.

Did you run the client-side data collector to check for any errors.? Please do check out this link https://techcommunity.microsoft.com/t5/azure-database-support-blog/azure-sql-db-connectivity-troubleshooting/ba-p/1158677 to help you troubleshoot and if the issue persists then you might need a support case for further troubleshooting. Regards,

Oury
saurabh patel 0 Reputation points

2024-01-17T15:24:56.6466667+00:00

I ran the SQL connectivity script, and unfortunately, I'm encountering a gateway error. I've attached the error message below. We've confirmed that our ISP provider has opened port 1433 on the corporate firewall, and I've also opened the same port on the VM itself. However, we're still facing issues. All VMs are hosted on VMware ESXi. I've opened a Microsoft support ticket, but I haven't received a solution from the MS team. That's why I've reached out here—hoping to get some new troubleshooting insights. Any ideas on what else we can do to resolve this? Testing (gateway) connectivity to 20.62.132.164:1433 -> TCP test FAILED Gateway connectivity to 20.62.132.164:1433 FAILED Please make sure you fix the connectivity from this machine to 20.62.132.164:1433 to avoid issues! Failure to reach the Gateway is usually a client-side networking issue (like DNS issue or a port being blocked) that you will need to pursue with your local network administrator. See more about connectivity architecture at https://docs.microsoft.com/azure/azure-sql/database/connectivity-architecture
KapilAnanth-MSFT 49,021 Reputation points Microsoft Employee

2024-01-31T06:12:11.24+00:00
@saurabh patel

Greetings.

Can you confirm if the OnPremVM has internet connectivity?

Open an elevated command prompt in this VM and run

curl -4 ifconfig.me

Or open a browser tab and Navigate to https://ifconfig.me/ and share the Public IP you are seeing.

Additionally, please share the results of tracert <SQL FQDN> and share the results please

Cheers,

Kapil

saurabh patel 0

yes, OnPrem VM is connected to Internet
Public IP : 64.206.82.161

  Microsoft Windows [Version 10.0.14393]
  (c) 2016 Microsoft Corporation. All rights reserved.
  
  I:\>tracert sptest123.database.windows.net
  
  Tracing route to cr14.eastus1-a.control.database.windows.net [20.62.132.163]
  over a maximum of 30 hops:
  
    1    <1 ms    <1 ms    <1 ms  10.2.50.1
    2    <1 ms    <1 ms    <1 ms  192.9.200.254
    3     6 ms     6 ms     6 ms  vcg96.nycm01-ny.us.windstream.net [209.156.206.75]
    4     6 ms     6 ms     6 ms  static-67-62-180-60.t1.cavtel.net [67.62.180.60]
    5     6 ms     6 ms     6 ms  192.168.251.0
    6     6 ms     6 ms     6 ms  192.168.251.1
    7     6 ms     6 ms     8 ms  h148.122.138.40.static.ip.windstream.net [40.138.122.148]
    8     7 ms     7 ms     7 ms  ae8.cr01.nycp01-ny.us.windstream.net [40.129.37.2]
    9     *        *        *     Request timed out.
   10    15 ms    15 ms    16 ms  ae86-0.ier02.bl32.ntwk.msn.net [104.44.199.91]
   11    15 ms    16 ms    15 ms  ae20-0.icr04.bl7.ntwk.msn.net [104.44.230.182]
   12     *        *        *     Request timed out.
   13     *        *        *     Request timed out.
   14     *        *        *     Request timed out.
   15     *        *        *     Request timed out.
   16     *        *        *     Request timed out.
   17    16 ms    16 ms    16 ms  20.62.132.163
  
  Trace complete.
  
  I:\>

KapilAnanth-MSFT 49,021 Reputation points Microsoft Employee

2024-02-01T10:16:19.97+00:00
@saurabh patel

The ICMP packet getting a reply clearly indicates that the connectivity is just fine.

However, you being not able to TCP Ping (port ping) the FQDN on Port 1433 indicates some application level configuration missing/required.

I would suggest you to wait for the Azure Support Team only.

Check the logs on what happens when you connect on the Port 1433

Are they even seeing the traffic originating from your IP or not? (they can log it from Platform)

Cheers,

Kapil
saurabh patel 0 Reputation points

2024-02-06T17:13:36.7333333+00:00

I've opened a support ticket with Azure SQL team, but unfortunately, they are also unable to resolve this issue. let me know if you have any other solution to resolve network issue

1 answer

Your answer

Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-12T17:15:43.3933333+00:00

@saurabh patel
Thank you for reaching out. Could you please share the error message you are getting. Regards, Oury
Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-16T20:15:42.74+00:00

@saurabh patel Just so I understand the problem - You have one VM that is unable to reach Azure Sql Database, while other VMs on the same host can reach it fine. Is that correct? If that is the case, then please run the client side data collector and check if flags any issues?
saurabh patel 0 Reputation points

2024-01-16T20:52:18.3233333+00:00

Hey, we're experiencing connection issues on all VMs, but oddly enough, we can connect to the same Azure database from a physical machine. Both VMs and the physical machine are connected to the same firewall. Any idea what's going on? Here's the error message: TITLE: Connect to Server

Cannot connect to tcp:name.database.windows.net,1433.

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: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

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
saurabh patel 0 Reputation points

2024-01-16T20:59:12.36+00:00

Hey, we're experiencing connection issues on all VMs, but oddly enough, we can connect to the same Azure database from a physical machine. Both VMs and the physical machine are connected to the same firewall. Any idea what's going on? Here's the error message: TITLE: Connect to Server Cannot connect to tcp: name.database.windows.net,1433. 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: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476 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
Oury Ba-MSFT 20,626 Reputation points Microsoft Employee

2024-01-16T21:45:51.7733333+00:00

@saurabh patel
Thank you for sharing the above details.

The above error message usually indicates a client-side networking issue, which you need to pursue from the client side. The most likely causes are the client platform being too slow to respond to the login traffic, or a problem with the network that misroutes or drops part of the network traffic.

Did you run the client-side data collector to check for any errors.? Please do check out this link https://techcommunity.microsoft.com/t5/azure-database-support-blog/azure-sql-db-connectivity-troubleshooting/ba-p/1158677 to help you troubleshoot and if the issue persists then you might need a support case for further troubleshooting. Regards,

Oury
saurabh patel 0 Reputation points

2024-01-17T15:24:56.6466667+00:00

I ran the SQL connectivity script, and unfortunately, I'm encountering a gateway error. I've attached the error message below. We've confirmed that our ISP provider has opened port 1433 on the corporate firewall, and I've also opened the same port on the VM itself. However, we're still facing issues. All VMs are hosted on VMware ESXi. I've opened a Microsoft support ticket, but I haven't received a solution from the MS team. That's why I've reached out here—hoping to get some new troubleshooting insights. Any ideas on what else we can do to resolve this? Testing (gateway) connectivity to 20.62.132.164:1433 -> TCP test FAILED Gateway connectivity to 20.62.132.164:1433 FAILED Please make sure you fix the connectivity from this machine to 20.62.132.164:1433 to avoid issues! Failure to reach the Gateway is usually a client-side networking issue (like DNS issue or a port being blocked) that you will need to pursue with your local network administrator. See more about connectivity architecture at https://docs.microsoft.com/azure/azure-sql/database/connectivity-architecture
KapilAnanth-MSFT 49,021 Reputation points Microsoft Employee

2024-01-31T06:12:11.24+00:00

@saurabh patel

Greetings.

Can you confirm if the OnPremVM has internet connectivity?

Open an elevated command prompt in this VM and run

curl -4 ifconfig.me

Or open a browser tab and Navigate to https://ifconfig.me/ and share the Public IP you are seeing.

Additionally, please share the results of tracert <SQL FQDN> and share the results please

Cheers,

Kapil
saurabh patel 0 Reputation points

2024-01-31T21:09:43.5633333+00:00

yes, OnPrem VM is connected to Internet

Public IP : 64.206.82.161

Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. I:\>tracert sptest123.database.windows.net Tracing route to cr14.eastus1-a.control.database.windows.net [20.62.132.163] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.2.50.1 2 <1 ms <1 ms <1 ms 192.9.200.254 3 6 ms 6 ms 6 ms vcg96.nycm01-ny.us.windstream.net [209.156.206.75] 4 6 ms 6 ms 6 ms static-67-62-180-60.t1.cavtel.net [67.62.180.60] 5 6 ms 6 ms 6 ms 192.168.251.0 6 6 ms 6 ms 6 ms 192.168.251.1 7 6 ms 6 ms 8 ms h148.122.138.40.static.ip.windstream.net [40.138.122.148] 8 7 ms 7 ms 7 ms ae8.cr01.nycp01-ny.us.windstream.net [40.129.37.2] 9 * * * Request timed out. 10 15 ms 15 ms 16 ms ae86-0.ier02.bl32.ntwk.msn.net [104.44.199.91] 11 15 ms 16 ms 15 ms ae20-0.icr04.bl7.ntwk.msn.net [104.44.230.182] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 16 ms 16 ms 16 ms 20.62.132.163 Trace complete. I:\>
KapilAnanth-MSFT 49,021 Reputation points Microsoft Employee

2024-02-01T10:16:19.97+00:00

@saurabh patel

The ICMP packet getting a reply clearly indicates that the connectivity is just fine.

However, you being not able to TCP Ping (port ping) the FQDN on Port 1433 indicates some application level configuration missing/required.

I would suggest you to wait for the Azure Support Team only.

Check the logs on what happens when you connect on the Port 1433

Are they even seeing the traffic originating from your IP or not? (they can log it from Platform)

Cheers,

Kapil
saurabh patel 0 Reputation points

2024-02-06T17:13:36.7333333+00:00

I've opened a support ticket with Azure SQL team, but unfortunately, they are also unable to resolve this issue. let me know if you have any other solution to resolve network issue

Answer 1

RahulRandive 10,321

Hi saurabh patel •, As you mentioned, you are able to connect to the SQL Server from the local environment but not from the VM's, indicating a potential connectivity issue or network problem between them. The error you provided is quite generic. To obtain a more meaningful error, please run the following network trace from the VM and analyze the networking issues from the output file or attach the results. This PowerShell script will run some connectivity checks from this machine to the server and database. https://github.com/Azure/SQL-Connectivity-Checker Thank you!

saurabh patel 0 Reputation points

2024-01-17T15:24:11.01+00:00

I ran the SQL connectivity script, and unfortunately, I'm encountering a gateway error. I've attached the error message below. We've confirmed that our ISP provider has opened port 1433 on the corporate firewall, and I've also opened the same port on the VM itself. However, we're still facing issues. All VMs are hosted on VMware ESXi. I've opened a Microsoft support ticket, but I haven't received a solution from the MS team. That's why I've reached out here—hoping to get some new troubleshooting insights. Any ideas on what else we can do to resolve this? Testing (gateway) connectivity to 20.62.132.164:1433 -> TCP test FAILED Gateway connectivity to 20.62.132.164:1433 FAILED Please make sure you fix the connectivity from this machine to 20.62.132.164:1433 to avoid issues! Failure to reach the Gateway is usually a client-side networking issue (like DNS issue or a port being blocked) that you will need to pursue with your local network administrator. See more about connectivity architecture at https://docs.microsoft.com/azure/azure-sql/database/connectivity-architecture
RahulRandive 10,321 Reputation points

2024-01-17T15:33:57.39+00:00

Hi saurabh patel,

As the error suggests a DNS issue or a blocked port, it requires investigation by network experts. You may find relevant information in this blog with a similar focus: https://www.mattmansoomi.com/port-being-blocked-for-azure-sql-database/

Additionally you can also check below Microsoft document https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/tcp-ip-connectivity-issues-troubleshooting

Also, as you mentioned, you have already opened a support ticket for this, could you please share case number? Thank you!
saurabh patel 0 Reputation points

2024-01-17T16:57:58.5633333+00:00

case number : 2312130030005849
saurabh patel 0 Reputation points

2024-01-17T16:58:47.4066667+00:00

case number : 2312130030005849
saurabh patel 0 Reputation points

2024-01-29T20:37:45.0333333+00:00

I've also whitelisted the necessary port (1433, 11000-11999) on one of the VMs, but unfortunately, we're still encountering the same network problem. Could you please advise on any additional steps we can take to resolve this issue?

Share via

Connection error when tried to connect Azure Database from On-prem virtual machine through SQL management studio

Hey, we're experiencing connection issues on all VMs, but oddly enough, we can connect to the same Azure database from a physical machine. Both VMs and the physical machine are connected to the same firewall. Any idea what's going on? Here's the error message: TITLE: Connect to Server

Cannot connect to tcp:name.database.windows.net,1433.

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

Your answer