ASP.NET 2.0 and connection to remote SQL 2000 server

[Mitya Mitriev]

Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the 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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=serverna me;Database=SOX ;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed on
production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?

[Henry]

Try changing the connection string to reflect the actual address to server,
that may include changing that information in the web.config file...

This is my connection string:

Server=ADDRESS TO SERVER!;Databas e=SOX;User ID=userxxx;Pass word=******;

"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:uT******** ******@TK2MSFTN GP04.phx.gbl...

Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the 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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=serverna me;Database=SOX ;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed on
production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?

[Mitya Mitriev]

Do you mean IP address? I tried, it didn't help :(

"Henry" <at************ **@hotmail.comw rote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRESS TO SERVER!;Databas e=SOX;User ID=userxxx;Pass word=******;

"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:uT******** ******@TK2MSFTN GP04.phx.gbl...

>Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the 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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=servern ame;Database=SO X;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?

[Patrick.O.Ige]

Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:ex******** ******@TK2MSFTN GP03.phx.gbl...

Do you mean IP address? I tried, it didn't help :(

"Henry" <at************ **@hotmail.comw rote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

>Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRE SS TO SERVER!;Databas e=SOX;User ID=userxxx;Pass word=******;

"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:uT******* *******@TK2MSFT NGP04.phx.gbl.. .

>>Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the 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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=server name;Database=S OX;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplicatio n which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?

[Mitya Mitriev]

Thank you, but I use Sql Server 2000.

"Patrick.O. Ige" <na********@hot mail.comwrote in message
news:Ou******** ******@TK2MSFTN GP04.phx.gbl...

Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:ex******** ******@TK2MSFTN GP03.phx.gbl...

>Do you mean IP address? I tried, it didn't help :(

"Henry" <at************ **@hotmail.comw rote in message
news:%2******* *********@TK2MS FTNGP04.phx.gbl ...

>>Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRES S TO SERVER!;Databas e=SOX;User ID=userxxx;Pass word=******;

"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:uT****** ********@TK2MSF TNGP04.phx.gbl. ..
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000
database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed
on another server.
I received the 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
connection s. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=serve rname;Database= SOX;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplicati on which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?

[Peter Bromberg [C# MVP]]

You have to make sure that the remote server is not "Hidden" which would
prevent a remote connection; also check that BOTH Sql Server and Windows
Authentication are enabled.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Mitya Mitriev" wrote:

Thank you, but I use Sql Server 2000.

"Patrick.O. Ige" <na********@hot mail.comwrote in message
news:Ou******** ******@TK2MSFTN GP04.phx.gbl...

Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:ex******** ******@TK2MSFTN GP03.phx.gbl...

Do you mean IP address? I tried, it didn't help :(

"Henry" <at************ **@hotmail.comw rote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..
Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRE SS TO SERVER!;Databas e=SOX;User ID=userxxx;Pass word=******;

"Mitya Mitriev" <aa*@stopspam.o rgwrote in message
news:uT******* *******@TK2MSFT NGP04.phx.gbl.. .
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000
database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed
on another server.
I received the 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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=server name;Database=S OX;User ID=userxxx;Pass word=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplicatio n which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?