How can I force my ASP.Net application to connect to a SQL Server using TCP/IP, not Named Pipes? I read somewhere putting "tcp:" in front of the server name in the connectionstring should do the trick, but it does not seem to change anything. Edit1: TCP/IP is enabled on the SQL Server. I tried Network Library=dbmssocn in the connectionstring, I still get an errormessage about named pipes: "provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server" Edit2: Turns out my problem was another hidden connectionstring used by entity framework

Reputation: 12384

Forcing ASP.Net to use TCP/IP to connect to SQL Server instead of named pipes

How can I force my ASP.Net application to connect to a SQL Server using TCP/IP, not Named Pipes?

I read somewhere putting "tcp:" in front of the server name in the connectionstring should do the trick, but it does not seem to change anything.

TCP/IP is enabled on the SQL Server.
I tried Network Library=dbmssocn in the connectionstring, I still get an errormessage about named pipes: "provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"

Turns out my problem was another hidden connectionstring used by entity framework

Upvotes: 11

Reputation: 1666

Just to add a quick hint, could cause issues, if you need to specify a port, do it after the IP address, and use a comma, not a colon.

Upvotes: 0

Reputation: 2981

You can force it in the connection string:

server=tcp:hostname

Upvotes: 26

Reputation: 3340

Use the SQL Server Configuration Manager on the client and disable the client protocols you don't want it to use.

Upvotes: 4

Reputation: 395

It depends how you're connecting to the database, but this should give the information you need.

Upvotes: 0