Remote Connection problem / question
-
Hi
I have a server with windows 2003 and SQL Server 2005 installed.
When I use the client on the server to connect to the database (using windows authentication) it does this no problem. And when remotely connecting (using SQL authentication) it 'seems' to do it no problem as well.
However in "SQL Sevrer Management Studio" on the server when I connect it displays the server name with a nice green circle with a little arrow inside. On the remote computer it 'seems' to connect but I don't get the green circle with the arrow next to the server (just get a white circle) - Hope this all makes sense.
I get the feeling I can 'see' the server but can't connect properly. Is this common behaviour (white circle) or have I made a 'school boy error' somewhere along the way!?
Any help/suggestions would be much appreciated. Thanks in advance!
Regards
Toby
-
Enable remote connections in the Configuration Tools\SQL Server Surface Area Configuration utility.
-
Surface Area Configuration is setup correctly (on the server):
Database Engine/Remote Connections => Local and Remote Connections - using both TCP/IP and named pipes.
-
Just to clarify where I am and what I have tried
Basically on the remote computer I log in with "sa" and it says it connects, but it doesn't look/behave like its connected. And on the server I log in with windows authentication and it connects no problem with full functionality.
The server is setup to accept remote connections. It uses both windows and sql authentication. I have tried playing around with the TCP/IP port numbers. I've stopped the windows firewall in administrative tools/services on both the server and remote machine. Also added sql drivers under the ODBC Data Source Administrator for both the client & server.
I am pretty much out of ideas and the problem is really starting to bug me. I can't be the only person getting this bug/problem!?
Thanks in advance
Toby
-
I get this same problem when I refresh the database (until then it shows the green circle), both local and remote.
Enabling the browser service seems to solve this so I think it tries to talks to the browser service to resolve its status and control the service?
-
Im using an 'alias' with a hard coded IP and port so I have the browser service disabled.
Although saying that, I started off by using the Browser service, but didn't have any luck
-
Seems like the problem is with the server being on a different 'Domain'
I will post more info when I finish troubleshooting it
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply