Pre-login handshake failed

Date Published: 01/16/2013 1:31 AM

I have two SQL Servers set up to do mirroring. This is working fine.

I also have a .NET web application hosted on a different server connecting to either DB server.

All of the servers are under one AD.

Here's the connection string that I use:

Data Source=10.0.5.XXX; Failover Partner=10.0.4.XXX; Database=YYY; Integrated Security=True;

When the web server is freshly started, I am not able to connect to the DB, and is getting the following error:

"The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time."

If I turned off the firewall on the principle SQL Server, the connection is then working perfectly fine. If I turned the firewall back on, the connection works for a while and at some point failed back to the original error message.

I'm trying to find out what additional port I need to open (I have the default 1433 open and also 5022 open for mirroring). Does anybody ever experienced this issue?

I've tried monitoring open connections via Resource Monitor and netstat, but never found any other port used other than 1433 or 5022.

View full answer on Server Fault

View Local Answers...

Can't find the answer to this question?

No answers yet.

Can you answer this question?

Pre-login handshake failed

  • Your Nickname
  • Your Answer

  • Enter the code below to prove you are human