Failing to connect to remote SQL Server 2000 from ASP.NET 2.0?

Question

I have a remote server running Windows XP SP2, with both SQL2005 Express with Advanced Features and SQL 2000 installed. I can remotely connect to the SQL2K instance using Query Analyser or Enterprise Manager. I can also remotely connect to the SQLEXPRESS using Management Studio Express Edition.

I am writing an ASP.NET 2.0 with VS2005 application (actually upgraded from .NET 1.1 with VS2003). However, now I cannot connect to the remote SQL2K from the application. I can connect to a locally installed SQL2K on the development machine, but I cannot connect to the remote server.

WITH NAMED PIPES DISABLED AND TCP/IP ENABLED IN THE SQL2K CLIENT NETWORK UTILITY
provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

WITH BOTH NAMED PIPES AND TCP/IP ENABLED IN THE SQL2K CLIENT NETWORK UTILITY (TCP/IP WITH HIGHER PREFERENCE THAN NAMED PIPES)
An error has occurred while establishing a connection to the server. When connecting to SQL2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I have also noticed that from VS2005 using the Server Explorer to add a data connection, I can only connect to the remote SQL2K if I use the OLEDB provider but not the SqlClient.

HOW CAN I FIX THIS? WHERE AM I GOING WRONG?

The problem is actually not the SQL 2005. My application needs to connect to SQL Server 2000. The error message I get seems to suggest that .NET 2.0 is actually 'thinking' its a SQL 2005

Answer 1

So... I am not clear from your information - have you or have you not enabled remote connections using the Surface Area Configuration manager for your SQL 2005 instance?