SQL Server Connection Timeouts

Question

Our SQL Server 2008 has been working for quite a while, but then we suddenly got connection timeouts.

We couldn't find an answer to the problem and ended up enabling Named Pipes just to get our applications working, but this is not a great solution (some apps we have to open twice, first time fails second time it fires up)

Anyone know what we can check to fix our TCP connections/configuration?

Were you connecting from your desktop or another database server? etc? — jl., May 25 '11 at 13:07
In the surface area configuration for services, what is it set to? — DanBig, May 25 '11 at 13:16
DanBig - Is surface area configuration still available in 2008? I know it 2005, but can't seem to find it for 2008? — Jacques, May 25 '11 at 13:33
Found the new surface area configuration. It's set to use TCP/IP and Named Pipes. The port for the specific IP range was set to dynamic, but I've now hard coded it to 1433 and it's still not working. — Jacques, May 25 '11 at 13:56
Are the desktops not connecting at all, or is the connection just unreliable? — Lucky Luke, May 25 '11 at 14:59
Are you using SQL Express edition? If yes, then turn off AUTO_CLOSE. — Sankar Reddy, May 25 '11 at 20:48

score 0 · Accepted Answer · answered May 31 '11 at 14:20

It would seem that I found an answer:

The server was using dynamic ports which we changed to use port 1433 only. We confirmed that inbound connections were enabled in the firewall settings. Disabled SQL Browser Tested the connection using Telnet and SQL Server Management Studio Then we switched the SQL Browser back on and tried the named instance login again and it worked.

Not sure why this was a problem, I assumed that dynamic ports should have worked with the SQL Browser Service

SQL Server Connection Timeouts

1 Answers1