🚀 go-pugleaf

With SQL Server for NT you Named pipes is
always loaded and in version 4.2x you can't
unload named pipes.  NWLINK is to NT what
NIK is to OS/2, and yes, it exists quite
nicely next to named pipes on the server
side.  NWLink is always chosen as the net
lib on the server side to talk to clients
on an IPX network.

On the client side, you must still pick
the network library appropriate for your
windows/netware configuration.  If you are
loading ODI drivers into low memory, you
should choose IPX/SPX from the client
configuration utility.  If you are using
WFW 3.11 and the virtual driver, you can
choose named pipes on the client side.

Use the client configuration utility
(w3dbver.exe) to make these changes in
windows clients, otherwise become familiar
with how network libraries from clients map
to servers in win.ini.

Mike Culver
Microsoft Certified SQL Server Trainer
Mercer Island, WA

<---- Begin Included Message ---->
From: David May <davidmay@ASTRO.OCIS.TEMPLE.EDU> wrote

>We may go to the Windows NT version of the SQL Server, does this solve
>the
>workgroup problem?

<---- End Included Message ---->