Unable to connect On-prem SQL server outside the local server getting connection timeout expired

Question

Hi Team

I´m facing a problem without solution

Connection Timeout Expired. 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. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1107; handshake=29721; (Microsoft SQL Server, Error: -2)

I am not able to connect SQL server from other than local machine. SQL Services are up and running.

I checked firewall settings, and everything seems ok from another machine.

Note: Both machines are in different domain.

Answer 1

Note: Both machines are in different domain.

That may be the issue. For cross-domain login to work with Windows authentication, there needs to be trust between the domains. And maybe a few more stars have to align,

Is the other SQL Server instance configured for mixed-mode authentication? If so, can yo create an SQL login and test with that login?

Also, can you test with a completely bogus server name in the other domain? This should obviously result in an error, but which error message? The same as above, or a different one? (I expect a different one, but I'd like to verify.)

Answer 2

Somebody might have modified the service account that sql server is using and kerberos authentication starts failing
if you can use SQL server from within the SQLHost then it is defineitely a kerberos problem

You can use this free tool from MS to analyze -- Microsoft® Kerberos Configuration Manager for SQL Server®
link is below

https://www.microsoft.com/en-us/download/details.aspx?id=39046

If you want to resolve it without the wizard you need to configure the SPN for sql server yourself.
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections?view=sql-server-ver16

Answer 3

Hi @Arun Singh ,

Have you tried logging in with your SQL account? If there is no problem with SQL account, then the problem is due to the fact that you have not set up mutual trust between different domains.

Best regards,
Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.