This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 69%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMF%3C/text%3E%3C/svg%3E)
A connection was successfully established with the server, but then an error occurred during the pre-login handshake
I am getting this error when testing from SSMS and also from linked servers and SSIS providers.
Around the 4th November, this connection stopped working. I see that TLS 1.0 and 1.1 were due to be deprecated on 31st October 2024 so I suspect this is related to this event.
However, I am getting this on a newly installed Dev server which is Windows Server 2022 and I am also seeing this on the Production server which is Windows Server 2012.
I have disabled the TLS 1.0 and 1.1 using IIS Crypto and also disabled in the registry using these keys
SCHANNEL\Protocols\TLS 1.1\Client
SCHANNEL\Protocols\TLS 1.1\Server
SCHANNEL\Protocols\TLS 1.2\Client
SCHANNEL\Protocols\TLS 1.2\Server
I ran the Azure Connectivity Checker. Here is the summary. Note that I get the warning about invalid gateway addresses on a working machine also. What is specific to the non working machine is the line that says
"DNS resolution using an external provider (OpenDNS) could not be verified, please verify if FQDN is valid and address is getting resolved properly."
Both machines are pointing at the same DNS servers and both return similar nslookup results (different gateway addressed, but I guess that can be expected)
######################################################
SUMMARY:
######################################################
Found DNS record in DNS server (IP Address:20.61.99.197)
Error getting DNS record in Open DNS (warp01.database.windows.net : This operation returned because the timeout period expired)
DNS resolution using an external provider (OpenDNS) could not be verified, please verify if FQDN is valid and address is getting resolved properly.
Connectivity to login.windows.net:443 succeeded (used for AAD Password and Integrated Authentication)
Connectivity to login.microsoftonline.com:443 succeeded (used for AAD Universal with MFA authentication)
Connectivity to secure.aadcdn.microsoftonline-p.com:443 succeed (used for AAD Universal with MFA authentication)
WARNING: 20.61.99.197 is not a valid gateway address
Connection to database master failed (error 64, state 0): A connection was successfully established with the server, but then an error occurred during the pr
e-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
######################################################
RECOMMENDED ACTION(S):
######################################################
DNS resolution using an external provider (OpenDNS) could not be verified, please verify if FQDN is valid and address is getting resolved properly.
WARNING: 20.61.99.197 is not a valid gateway address
In case you are not using Private Endpoint, please make sure the server name FQDN is correct and that your machine can resolve it to a valid gateway IP addre
ss (DNS configuration).
In case you are not using Private Link, failure to resolve domain name for your logical server is almost always the result of specifying an invalid/misspelle
d server name,
or a client-side networking issue that you will need to pursue with your local network administrator.
See the valid gateway addresses at https://docs.microsoft.com/azure/azure-sql/database/connectivity-architecture#gateway-ip-addresses
See more about Private Endpoint at https://docs.microsoft.com/en-us/azure/azure-sql/database/private-endpoint-overview
Connection to database master failed (error 64, state 0): A connection was successfully established with the server, but then an error occurred during the pr
e-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
If this is a database engine error code you may see more about it at https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events
-and-errors
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 49%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
Hi Mike Fleming,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Could you please provide more details on the issue? If possible, any screenshots or additional information would be greatly appreciated, as it will help us conduct a more thorough investigation.
Hi @Mike Fleming,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Hi, this turned out to be a firewall issue. I was sidetracked by the fact that test-netconnection worked, but the application was blocked on the firewall.
Thanks for your response.