A network-related or instance-specific error occurred while establishing a connection to SQL Server

Our WEB master is setting up a new server. The new server is working as it should except for she is now trying to run some code in ASP.net. SQL 2000 and server 2003

I get my telnet connection to the SQL server. Server I on the DMZ and the data base is on my domain.
Network team tells me that we have all of the right ports open. Please see below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
fischerbobAsked:
Who is Participating?
 
Jim P.Connect With a Mentor Commented:
The issue is the Named Pipes. You should turn named pipes off and use only TCP/IP. Named Pipes uses domain authentication directly off the AD controller then to the SQL Server. Where TCP/IP gets the authentication request from the server/app through the TCP and then sends to the AD controller for the verification of credentials.
0
 
fischerbobAuthor Commented:
we also had a problem with the WEB config file. All is good now thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.