Carlos

SQL 2005 Remote Connections

I have this irritation with SQL 2005 and remote connections. Maybe its something I am doing incorrectly (which is very possible).

Everytime I install a new SQL 2005 server and then try using an application that I have developed to connect to that SQL 2005 machine, I get a SQL Protocol Error 25, “Cannot find the SQL server or the instance specified”.

The environment

1. Windows 2003 Forest/Domain (Single Forest Single Domain SFSD)
2. SQL 2005 Server (with SP1) and when installing SQL 2005 I check “Enable Remote Connections”
3. 4 Different Windows clients (from Windows XP to Windows 2003)
4. Application developed using .net 2.0
5. Application is doing a normal SQL connect and Select * from SomeTable

I first thought it was because I was only using the ServerName in the connection string i.e. "MyServer", but then tried the following:

1. Myserver
2. Myserver.mydomain.myname.com (Fully Qualified Domain Name {FQDN})
3. Myserver\<SQLInstanceName>
4. Myserver.mydomain.myname.com\<SQLInstanceName>
5. Ip_Address
6. Ip_Address\<SQLInstanceName>

With all these I get the same ERROR (See above), I triple check on the server properties that "Allow remote connections" is checked!

 So what I have found works EVERY time is go to: SQL Server Configuration Manager > SQL Native Client Configuration > Aliases > Create New Alias.

I then create a new Alias with the Name being the NetBios name of the server. I then restart the SQL services, and PRESTO!

All of a sudden all the clients can see the SQL server and connect as they should be doing.

I just want to know:

1. What am I doing wrong
2. Is this normal behavior
3. Is this "by design"
4. What am I missing here?

Frustrated!
Carlos Magalhaes