SQLServer Express remote connection problems

November 2, 2006 3:09 AM

SQLServer Express remote connection problems. Please hope me!

I want to connect to my server running SQL Server Express 2005 with Aqua data studio, but i just can't get my server to accept remote TCP connections. I've tried everything, but it's still not working!

I've done everything on this page. I've tried telnetting into port 1433 but it just times out.

Does anyone have any idea how i can get my server to start listening to me!!

thanks

posted by derbs to computers & internet (9 comments total)

Does it work locally, i.e. if you install Aqua data studio on the same machine?

What's the exact address you connect to? SQL Server Express is by default installed as a named instance called \SQL-Express. Maybe you tried to connect to the server name, while you have to connect to servername\sql-express.

What's the exact error message?
posted by Herr Fahrstuhl at 4:51 AM on November 2, 2006

Is there a firewall up on the machine hosting SQL Server? If so, is there an opening for 1433?
posted by mkultra at 6:45 AM on November 2, 2006

Ethereal will tell you where your packets are going, and will also let you follow any TCP conversations that actually end up happening.
posted by flabdablet at 6:51 AM on November 2, 2006

Ditto mk. You can run superscan on the box and see what ports are responding. Version 3 has a nicer (IMHO) GUI.
posted by mrbugsentry at 7:20 AM on November 2, 2006

I don't think the firewall is running (it's windows server 2003 btw). When i open the firewall control panel it says the service is stopped, so i'm guessing it's not running...

Aqua data studio (and the microsoft management) connect fine on the machine. It's just port 1433 isn't responding
posted by derbs at 8:36 AM on November 2, 2006

You said you can connect using Aqua Data Studio from the server console. Is this connecting via TCP/1433?

Do you have an IP security policy in place? You can check this under Administrative Tools ... Local Security Policy ... IP Security Policies

Are the server and the remote client on the same network segment? If not, is there a firewall between them?

Are you able to connect to any other services on the server, like Remote Desktop?
posted by me & my monkey at 8:52 AM on November 2, 2006

If Management Studio is able to connect remotely, but not via TCP/1433, it has to go through named pipes (i.e. NetBIOS over TCP/IP remote procedure calls) which use ports 137-139 and 445, IIRC.

Anyway, if you get a connection, where is the problem? You wrote in your original post that you couldn't connect at all?!
posted by Herr Fahrstuhl at 9:01 AM on November 2, 2006

YES you've nailed it! It was the IP Security Policy.

Good work man!!!
posted by derbs at 9:01 AM on November 2, 2006

oops sorry marked Herr Fahrstuhl's as best answer, the real best answer is me & my monkey's!! :)
posted by derbs at 9:07 AM on November 2, 2006