September 3, 2008 at 8:20 am
Hi Everyone,
I am trying to connect a managment studio client (patched to build 3159, post sp2 hotfix) to a remote sql 2005 std x64 server (patched to same build.
A normal connection
SERVERNAME\InstanceName
does not work
however when I specify a port number
SERVERNAME\InstanceName,10007
The connection works
Any ides why?
Cheers
Chris
September 3, 2008 at 4:35 pm
what happens when you try
server\instancename?
Have you set the instance to use a static port or dynamic?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 4, 2008 at 1:18 am
September 5, 2008 at 10:52 am
We had a similar problem almost 2 years ago when we upgraded from 2000 to 2k5 32 bit. It turns out that there was something in our foundry or firewall that wasn't configured correctly in the network traffic forwarding. Check with your network people, have them do a trace while you try to connect both ways. They should be able to see where the traffic is falling apart.
Also, you might try using a tracert on your box to see how far both attempts are going. Use both name & IP, one with and one without the port #.
September 5, 2008 at 2:23 pm
As Brandie points out it may be a firewall issue, are you able to telnet to port 1434 on the box you are trying to connect to the SQL instance, this is the port the sql browser listens on, if it blocked then when you pass the servername\instancename the browser service cannot give the client the port # the sql instance is listening on. Most of our server reside behind firewalls and 1434 is locked down, instead of messing with netwoork team we simply use SQL aliases.
September 6, 2008 at 12:36 pm
Try some more methods...
1) You can specify np: infront of your server name when connecting to SQL Server to forcibly use Named Pipes as Protocol. Check whether it is working...
2) Without specifying port number try tcp:server\instance and see what happens.
3) Turn off Windows Firewall/Virus Scanner Port Blocking Service and see how it goes.
4) Try to connecting to the server when you are within server using tcp:server\instance and see what happens. (If tcp is not specified then it may use shared memory)
5) telnet from source server to destination server on port 1434 and check whether you are getting black screen.
List your results.. then we shall decide what next..
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
September 7, 2008 at 3:49 am
just my 2 ct
Max Mulawa (9/4/2008)
Does 'SQL Server Browser' service is running on your remote server?
You can connect using the actual instance port number, so my guess would be you didn't open your firewall for the UDP port sqlbrowser is using.
(edit added the url)
http://msdn.microsoft.com/en-us/library/ms181087.aspx
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 25, 2008 at 1:20 am
When troubleshooting connectivity issues with SQL2k5, SQL2k8 I would recommend checking following MSDN article:
SQL2k5 - Troubleshooting: Timeout expired
http://msdn.microsoft.com/en-us/library/ms190181(SQL.90).aspx
SQL2k8 - Troubleshooting: Timeout expired
September 25, 2008 at 7:08 am
Sorry for my late reply,
The only seems to apply to a few users - all of them on the same network as the server (no firewalls between).
The issue doesn't affect me or the number of apps that don't specify a port.
its all very strange
Cheers
Chris
September 25, 2008 at 7:41 am
Try dumping their DNS cache and see if that works. It might be that these servers have a specific DNS name that hasn't (for whatever reason) been refreshed on those user's machines.
December 18, 2008 at 8:26 pm
We got this problem today and we could not find any issue with the server. It all started with the general SEMAPHORE timeout expired error and no access to any users and we have enabled dynamic ports. We are behind a firewall.
We tried moving the server to another node in the active -active cluster and it is running fine there. But, when we tried to move back to the same node, it is failing.
Finally, we had to restart that node and then we were able to move that instance back to the original node.
Why this could have happened? The error logs and event viewers, reports failures to connect to the browser but not the root cause?
Any help?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply