ASP.NET 2.0/SQL Server 2000 Connection Problem.

Hi All,


I have an ASP.NET 2.0 web application on a web server and a separate machine for SQL Server 2000 Database. I am using a Connectionstring based on Sql Authentication to connect to the the SQL 2000 Database.

Now, When I open the web page on the Web Server itself, I am able to successfully connect to the Database which confirms that the connection string is correct. However when I open the same web page from another client machine other than the web server, I get the following error message:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, 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) - .Net SqlClient Data Provider"

if I try to force TCP/IP specifying "Network Library=DBMSSOCN;" then it does not work at all from any machine and I get the following error:
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) - Net SqlClient Data Provider"

SQL Server is on default port 1433 and both TCP/IP and Named Pipes protocols are enabled.


Any advice on this is much appreciated.

Thanks,
Vikram

.

Relevant Pages

  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Classic ASP connectionstring to SQL Server 2005
    ... So this connection string is in the VB6 dll? ... What is the error message? ... Provider cannot be found. ... can you ping the sql server? ...
    (microsoft.public.inetserver.asp.db)
  • Re: Error while connecting remote SQL server
    ... There might be possoble you have defined aliases for the SQL server in your ... An error has occurred while establishing a connection to the server. ... (provider: Named Pipes Provider,error:40-Could not open ... (provider: Named Pipes Provider, error: 0 - No process is on the other ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Error while connecting remote SQL server
    ... SQL Server does not allow remote connections. ... (provider: TCP Provider, error: ... An error has occurred while establishing a connection to the server. ... (provider: Named Pipes Provider, error: 0 - No process is on the other ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
Loading