Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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?

share|improve this question
    
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
    
jl - we're connecting from desktops –  Jacques May 25 '11 at 13:31
    
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
show 2 more comments

1 Answer

up vote 0 down vote accepted

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

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.