Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 2005 Remote Connection issue

Author  Topic 

ryan.gillies
Starting Member

27 Posts

Posted - 2013-01-21 : 04:55:21
Hi all

I'm in an extremely puzzling and difficult situation and need some help on how to resolve it - the goal is simple; allow remote connections to a SQL Server 2005 server.

The issues:
- I'm doing some work for a company in Taiwan, so all the system UI is in Chinese.
- The server I'm working with is actually the backend to an old piece of software they purchased, tech support is at best extremely minimal.

Ok so I've connected to the server using SSMS and the local windows login as authentication fine. I can see all of the databases utilised by the software.

I've created a read-only sql server user and can log on with the user via SSMS. When I try to connect remotely using this logon however the connection fails.

Windows firewall is disabled on this machine, and I can ping it successfully.

To enable remote connections I first ensured the option was ticked in SSMS. Then I've tried to use the Surface Area Configuration tool (new to me, I've only ever used 2008 Express previously) however it provides an error in Chinese, which I've translated to the following:

"No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer."

At first my research found it was a potential Service Pack error, and have upgraded to SP2 - no luck.

I've now found the following potential solution after a bit of digging, it seems to have an issue with the NETWORK SERVICE user not having correct access: http://support.microsoft.com/kb/941823

I've looked in the Group Policy Managment Console to try enable the correct features, however SQL Server isn't listed anywhere.

To confound and puzzle matters further, when I check for the services in SQL Service Configuration Manager, there doesn't appear to be any!

I'm at a loss... if anyone has any inspired ideas I'd love to hear them!

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2013-01-21 : 10:54:30
Can you ping both with ip and fully qualified name?
Can you try a telnet test ?
Here are some other ideas - http://www.sqlserver-dba.com/2012/05/cannot-connect-to-sql-server.html

Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page

ryan.gillies
Starting Member

27 Posts

Posted - 2013-01-21 : 20:39:21
Thanks for the suggestions Jack, listed in order:

Ping to IP - 4 packets sent, 4 received.
Ping to Name - 4 packets sent, 4 received.

Telnet - I'm unfamiliar with Telnet - I use the telnet command to connect to the server (telnet 192.168.1.11 1433) and the screen shows only a flashing cursor, unable to type any further commands from there. I don't know if that's a sign that its forever connecting and going nowhere or if I'm doing something wrong.

SQL Services - as I mentioned in the earlier post, SQL Service Configuration Manager does not show any SQL Services, however SQL 2005 Service Manager (http://sql2005srvcmngr.codeplex.com) is installed and shows the services are running.

Connect from the server - able to connect using the local windows authentication and via the read-only sql authenticated username I created.

Authentication mode - as the above would indicate, I've checked and both windows auth and sql auth is permitted on the server.

Server versions - I'm attempting to connect remotely to the 2005 server from a machine running 2008 server and SSMS.

Network config - TCP/IP and Named Pipes are setup correctly.


All worthwhile things to try, but unfortunately still no cigar!

--------

Edit: Restarted both machines again and everything is working a-ok! Typical, thanks for the help anyway!
Go to Top of Page

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2013-01-22 : 09:50:18
@ryan.gilles - Sounds like yopu got the problem sorted. Strange , had you rebooted it before?
Assuming the port was 1433 - what you're seeing on Telnet looks right

Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page
   

- Advertisement -