🚀 go-pugleaf

There is a Technet article on this problem. I can't remember the exact cause
but, try updating the following files on your WFW client.
When we did this the problem went away.

NDIS     386        27,846 09-04-94   8:07a
NET      EXE       450,262 09-04-94   8:07a
NETAPI   DLL       109,120 09-04-94   8:07a
NWNBLINK 386        37,964 09-04-94   8:07a
VNETSUP  386        14,647 09-04-94   8:07a
VREDIR   386        85,746 09-04-94   8:07a



kormuth <kormuth@fmis.facmgmt.pitt.edu> wrote:
>
> I am having difficulty getting SQL Server client Tools to access the 
> server via named pipes.  I have tested network named pipes using
> readpipe from within WFW and makepipe from NTAS.  The NT makepipe 
> utility reported that data was read, but WFW readpipe reported back 
> the following error:
> 
> Network Error on drive ?
> 
> read failed, status error=58
> 
> 
> I get the same 'Network Error on drive?' when I try to connect to
> the SQL server from one of the WFW client tools.  When the error
> occurs, I get the cancel/retry option. When I chose 'retry',
> the NT Netwatch utility reported that:
> 
> IPC$ (remote IPC) - in use
> Admin from \\fm35 - admin account logged in from fm35 machine
> \pipe\sql\query - file open for use
> 
> 
> Thus, the pipe was established, but I am still not sure what 
> is causing the network error.  Any information would be greatly 
> appreciated.
> 
> 
> thanks,
> Jennifer Kormuth
> 
>