Clients connect via Named Pipes even though its disabled

We've got SQL 2000 clients (standard install, no sp) who are connecting
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?
Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegr oups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>