Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem

Hi,

have you refered below links

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer I tried to set the port using clientconfig.exe but that doesn't seem to work.

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.