-
Getting Rid of Named Pipes
We are running our SQL Servers (6.5, sp4) on a Wide Area Network and I want to force workstations to connect through TCP/IP (not Named Pipes)from the SERVER.
I have removed Named Pipes (through SQL Server setup) from the server.
If I do a "netstat -a" at the server I still get the following:
TCP ect_lon_sqln:nbsession ECTLONA1K:2181 Established
TCP ect_lon_sqln:1433 ECTLONA1K:2968 Established
Showing that I am getting one TCP/IP connection and one Named Pipes connection (the nbsession). I am certain that these are Named Pipes connections because these are the connections that I get when I only have
named pipes enabled.
The only way that I have found to get around this is by specifing in the connection string: "ncacn_ip_tcp:server_name" from within SQL client config.
How can keep my workstations from getting these connections without having to go to all of the workstations?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|