Can't connect to any SQL 2005 or 2000 databases :-(

Thursday, December 15, 2005

SQL 2005 works well on my machine, but I am abolutly unable to connect to any remote SQL 2005 or SQL 2000 instance. I tried to connect to my wireless laptop (I removed any Firewall to be sure about the issue) but nada, nothing happens.

It’s really annoying becuase the SQL 2000 instance I try to connect to works perfectly well since 3 years. What has changed in SQL 2005 instances name, I don’t know, maybe this is the problem. I used of course the Surface Area tool and everything seems to be OK on this side. strangely in the Connect to Server wizard, I can browse and see my other SQL server instance (name is like SQL\SQL) but whatever the options I pick always an error.

Any help?

8 Comments

Have you recently installed any spy-defence software?

Ali Parvaresh - Thursday, December 15, 2005 4:05:00 AM

Did you remove firewall BOTH on your and remote machine?

I was figthing with that problem about two weeks ago. It helped to open 1433 ports on both machines. No go with only the server one.

Michal Chaniewski - Thursday, December 15, 2005 10:24:00 AM

Michal yes I removed all firewall from both sides. I did the tests in two different network environment na dit's the same. I was thinking it coul be something in my office network but here at home the same.

Travis thanks I will try the link! Ali yes I have maybe some anti spyware installed but I don;'t see any troubles there. I don't have any biig ones like Norton antivirus or Norton Firewall.

Paschal - Thursday, December 15, 2005 10:40:00 AM

I ran into a similar problem. I ended up creating aliases using the Client Network Utility tool and explicitly setting the port using TCP. (uncheck the "Dynamically Determine Port" checkbox)

Sean Price - Thursday, December 15, 2005 4:26:00 PM

It happened to me once installing MS Anti Spyware on a Win2003 server. It blocked 1433 transactions even to the local. I had to reinstall SQL :(

Try netstat -a when you are trying to connect to the SQL see if port 1433 is being requested.

Ali Parvaresh - Friday, December 16, 2005 3:27:00 AM

after sql express is installed, it can only be connected locally.(using shared memory). you need enable the TCP/Named pipe connection manually

Russel - Friday, December 16, 2005 7:03:00 AM

Did you try netstat command ?

Ali Parvaresh - Saturday, December 17, 2005 3:10:00 AM

Hi Ali yes I tried and yes I don't see any requests with the port 1433. So something wrong there! Any idea?

Paschal - Saturday, December 17, 2005 6:39:00 PM

Comments have been disabled for this content.