Cant connect to database

Ok I have several sites on a server that have connected to databases on a different server for a long. Out of the blue today none of the sites on the server can connect to any databases on the other server. However, sites on other servers can connect to databases on the same db server.

This is the message I get:

An error has occurred while establishing a connection tothe server. When connecting to SQL Server 2005, this failure may becaused by the fact that under the default settings SQL Server does notallow remote connections. (provider: Named Pipes Provider, error: 40 -Could not open a connection to SQL Server)

The database server runs SQL Server 2000not2005 I can connect to the database from desktop (with an asp.net application or sql server management studio), I can ping the database server fine from the production web server, but my applications can't connect for some reason. There is nothing in the event log to suggest a problem, any ideas what could be causing this?

Take a look

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dotnet.framework.adonet&tid=0eaef762-1a7e-4391-8377-10a4080aed40&p=1

|||

I saw that in my searching, I don't have access to the production database server and it works fine from every other computer. The network people tell me everything on the firewall looks normal, so I think that means it has to be an issue with the web server, I'm just dumbfounded by why this would happen so suddenly.

|||

Hi,

From your description, since other website server can connect to the database server, so it seems that the issue is not caused by database server side.

I don't know what kind of security mode you use in your connection string, you have mentioned that you were managed to connect to the database via enterprise manager, are you using SQL authentication? If you are using Integrated Security in your connection string, can you make sure if the account of your web server has the access right to the database server. If you assign your database's userid and password explicitly, can you make sure if the user has been listed in the Logins list of your database server?

Actually, in order to check the issue, you may deploy the application which can't connect to the database to another web server, and try to check if it can work. If it can, the problem should be caused by the settings of that web server.

Thanks.