TCP and Named Pipe

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dcraig - 27 Jul 2005 18:30 GMT

We have VB clients connecting to a SQL 2000 server and some are using named
pipes and some are using TCP? does any one know why this would happen?

Thanks

Reply to this Message

David Gugick - 27 Jul 2005 21:18 GMT

> We have VB clients connecting to a SQL 2000 server and some are using
> named pipes and some are using TCP? does any one know why this would
> happen?
>
> Thanks

The SQL Server Client Network Utility lists available protocols and the
preferred order. Check that applet first. If you don't have the SQL
Server Client Tools installed on the client PC, check the reg key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

and look at the "ProtocolOrder".

Signature

David Gugick
Quest Software
www.imceda.com
www.quest.com

Reply to this Message

Dcraig - 28 Jul 2005 10:35 GMT

Thanks David,
The protocall order is TCP, NP
Most of our client pc's connect via TCP but ocasionally some connect via
Named pipes
and some via TCP. We have noticed a performance issue when named pipes are
in use.

The client PC's don't use sql clients or sql software?

Thanks

> > We have VB clients connecting to a SQL 2000 server and some are using
> > named pipes and some are using TCP? does any one know why this would
[quoted text clipped - 8 lines]
>
> and look at the "ProtocolOrder".

Reply to this Message

David Gugick - 28 Jul 2005 14:37 GMT

> Thanks David,
> The protocall order is TCP, NP
[quoted text clipped - 4 lines]
>
> The client PC's don't use sql clients or sql software?

You can try forcing the protocol in the connection string using "Network
Library=" in the connection string.

Signature

David Gugick
Quest Software
www.imceda.com
www.quest.com

Reply to this Message

Tim - 28 Jul 2005 20:44 GMT

Run C:\WINDOWS\system32\cliconfg.exe
or just cliconfg.exe to bring up Client Network Utility.

It is part of MDAC now.

Tim S

Reply to this Message