Quantcast
Channel: Foro de SQL Server Data Access
Viewing all articles
Browse latest Browse all 158

Login timeout expiration

$
0
0

We are getting the following error message sporadically:

 

Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 6108 ms, enqueued 1 ms, network writes 1 ms, network reads 6108 ms, establishing SSL 6107 ms, negotiating SSPI 0 ms, validating login 0 ms. [CLIENT: #.#.#.#]

 

We are seeing this message because we enabled some DBCC trace flags to try and figure out why our clients are having their connections terminated to the SQL 2005 (x64) server we have in production. It appears that the establishment of SSL is taking a very long time according to the log entry. What is using SSL? I'm assuming it is trying to communicate with one of my domain controllers and I'd like to know what perfmon counters i should watch to see what's going on. Is it making an LDAPS connection or kerberos? Or native ntlm?

 

We've already updated the NIC drivers/firmware and disabled the TcpChimney setting mentioned in the KB articles, but nothing so far has had an effect. I'm now trying to figure out if my DC is overloaded but don't know what counters to look at.

 

Thanks

Steve


Viewing all articles
Browse latest Browse all 158

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>