Connecting to a named instance

[yuna]

I have SQL server 2000 installed on a server, and I have an ASP .NET application on a web server that is tring to connect to a named instance on the database server.

However, I get the "Server Does Not Exist" error. I know that on my local machine, i've set up a TCP/IP alias using the Client Network Utility using the specified port and it works fine. However, the web server does not have any client utilites installed so I cannot create an alias as I did on my local machine.

Is there a workaround for this?


Any help is greatly appreciated. Thanks

 

[mrdenny]

Make sure that there are no firewalls blocking between the web server and the SQL Server. Specifically you'll need the following open.

UDP: 1434
TCP: 1433
TCP: (What ever port you are using for the named instance)

I'd also recommend having SQL only listen on TCP that way you don't have to worry about having NBT open between the web server and the SQL Server.

Unless you are connecting from an NT4 or SQL 7 server to a named instance you don't need to setup an alias in the client network utility unless you are blocking the UDP 1434 port.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[yuna]

Thanks for your quick reply.

However, I dont think it's a Firewall issue.

We're using Sql Server 2000. My problem is that we don't have the Client Network Utilities installed on the web server whereas it's installed on my development machine. So when I create a TCP/IP alias with port 1433 (that's the port we're using for the named instance) on my development machine, it works just fine. But, since the web server doesnt have the client network utilities installed, I couldnt create the alias for the named instance.

How would you go about this? Do I really need to install that on the web server?

 

[SQLBill]

For my clients that use Crystal Reports, I set up an ODBC connection on their computer.

-SQLBill

Posting advice: FAQ481-4875

 

[yuna]

Actually, we do have a firewall setup, and i'm not sure if we're blocking those ports.

If it is, is there a way to get around it ?

 

[SQLBill]

1. Have the firewall people open the port.
2. Have the firewall people open the port just for your application.
3. Change the port on the SQL Server instance to one not being blocked.

Three is your best option. The default SQL Server ports are well-known to hackers, so most firewall people don't like openning those ports (Microsoft made it a default of their XP firewall to turn those ports off. Which ought to indicate openning them isn't the best practice).

-SQLBill

Posting advice: FAQ481-4875

 

[mrdenny]

dido what SQLBill said. If the firewall is blocking the ports no matter what you are doing it won't work.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com