Board index MS SQL Server

unable to disable named pipes as default client protocol

unable to disable named pipes as default client protocol

Post by sabb » Thu, 31 Jan 2002 10:41:04



sql 2k query analizer and entrprise manager
keep on using named pipes as default protocol when connecting to
a database server running sql server 7 ,
even if named pipes have removed as available protocols on the client side,
(tcp/ip has been set as the only client proptocol ).
how's that ? any idea ?

--

http://www.sabbasoft.com : MTS - COM+, VBCOM, Security FAQ & more

 
 
 
Top

1. Disable Named Pipe Protocol in SQL Server

Can Named Pipe protocol be disabled is SQL Server?
(Disable it using server network library utility)

Thanks.

2. SQL*LOADER ERROR-524

3. Removing Name Pipes as the default protocol

4. UNIX REFER - format to MS ACCESS or DBASE

5. IIS4 - SQL Server still using Named Pipes even after changing default protocol to tcp/ip

6. Strange copy of Configuration file

7. Require Protocol for Name-Piped or Multi-Protocol

8. HELP TO FIND THE BEST DATABASE

9. Change Default Client Protocol or installing Client Utils

10. protocol: named pipes problem

11. Named pipes protocol and Opportunistic locking PLEASE HELP

12. Network protocol named pipes

13. looking for documentation regarding VDI and named pipe protocol


All times are UTC
Board index