This is SQL Server 2012SP4 on Windows 2012R2, with .NET Framework 4.7.02053.

I've RDPed into the database VM and open SSMS.

  • It times out with this error the first time I try to connect.
  • If I try again, it works.
  • If I increase the connection timeout, it works.

But why is it happening locally? This migrated from SQL Server 2008 and Windows 2008R2 and did not have this problem. Since a canned application that can't specify the connection timeout is failing, we need to solve this.

IPv6 is disabled both at the Windows level and in SQL Server Config Manager.


enter image description here

enter image description here

  • Are you connecting with AD creds? Maybe you have a delay going to the AD server for Authentication. On the 2nd attempt the authentication is cached on the local server. Apr 10, 2018 at 17:36
  • @JasonBluefire it happens both with AD and SQL Server authentication, using IP addresses and names.
    – RonJohn
    Apr 10, 2018 at 21:35
  • Interesting. You covered most anything else I can think of. Hopefully, someone else chimes in. I have to ask though, does the server have adequate resources? Is the RAM, CPU, or Disk IO tapped out? Same thing for the VM host. Apr 11, 2018 at 1:18
  • 3
    What edition of SQL Server? Is it express edition by chance or are any of the databases set for auto_close? Apr 11, 2018 at 16:01


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.