Forum Discussion

Copper Contributor

Apr 13, 2023

SQL Server Connectivity Issues - Ideas

I have to admit that have no knowledge about connectivity and setup of remote SQL servers. I usually have everything set up by knowledgeable IT support. In my current case the best I can say about t...

LainRobertson

Silver Contributor

Apr 13, 2023

Marie_Mittendorf

Hi, Marie.

Error 53 indicates the remote host running SQL Server cannot be found, which in turn usually relates to not being able to resolve the DNS name of that host.

Using my example below, the remote SQL Server host name is rpsql02.robertsonpayne.com:

Checking this name in PowerShell confirms that the DNS name does not exist, hence the SSMS error 53:

I'd recommend using Resolve-DnsName as depicted above (using your own server's host name, of course) to confirm if the remote SQL Server host name can be resolved.

I doubt you'd be in a position to fix this, but the output from Resolve-DnsName should help your service provider remedy the issue.

There are hacks for getting around this kind of issue but that's not a good path to pursue, so I'll avoid talking about those for now.

Cheers,

Lain

Marie_Mittendorf

Copper Contributor

Apr 13, 2023

LainRobertson

Thanks for the explanation so far. Anything around that topic will help me to address what needs to be done.

Seems like one information was missing from my side:
I'm not using the server name, but the IP for remote access. Actually, because the server name didn't work, but I didn't think of it as an issue if I had the IP, because that happened in the past as well with better support than now.
Therefore I checked PowerShell first with the name which gave the result: DNS Server Failure

and with name and IP which resulted in a time out

Any further info I might need?