Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sql connection time out error; fix with reboot

Status
Not open for further replies.

jl3574

Programmer
Jun 5, 2003
76
CA
I have a windows 2008 server running sql server 2008 and runs perfectly fine call this SERVER1. SERVER1 also is setup with running WEBserver IIS, DHCP, and DNS. I just set up another server running windows 2008 call this SERVER2. On Server2 i install sql management studio and runs perfectly fine and connects to SQL on SERVER1 with no issues.

Next i decided to set up a secondary DNS server on SERVER2. that was setup with success now when SERVER1 is shutdown SERVER2 's DSN continue to allow all the computers on the network to communicate properly.
ISSUES:
on SERVER2 i use sql management studio quite often to make changes to the SQL SERVER database on SERVER1 SINCE i installed the DSN server the connection to SERVER1 often times out for no particular reason.
i can ping SERVER1
when i try to connect to SERVER1 with sql management studio it will give me a time out error -2. the only way to fix this issues is to restart SERVER2 and everything will work fine for like a few hours.
not sure if there is a conflict with DSN that is causing this? my set up on the SERVER2 is static ip(obviously) with primary DSN(SERVER1's ip) and secondary DSN(Server2's ip).

SERVER1 SQL settings i have it enabled on TCP,name pipe, shared memory, I have SQL SERVER BROWER, SERVER AGENT all running.

Any feedback would be great thanks.
 
Have you checked your windows system event log.

Click Start
Type: eventvwr.exe
Click OK
Expand "Windows Logs"
Click on system.

If something "funcky" is going on with DNS, you will likely find errors getting logged.

When you get the timeouts connecting SSMS to the other server, can you try connecting to the other server by IP address. For example, if you normally connect "SERVER1", try connecting to "192.168.x.y". If you have a named instance, then include that in the server name like this: "192.168.x.y\SQLExpress".



-George
Microsoft SQL Server MVP
My Blogs
SQLCop
twitter
"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top