Windows XP and Netware --- UGH

[Robert Haussmann]

> Well I was hoping someone might give me a little help on this.
> 
> The system had had a number of Windows98 boxes changed to 
> WindowsXP in 
> recent weeks.
> 
> We are getting errors on the XP's that read as follows:
> 
> A system error has occurred ****
> 
> Cannot access menu
> P:/fp/menus/PA: Error Number-1
> Windows Error #53
> the network path was not found.
> 
> Now the file does, indeed exist, and the path is correct.  We get 
> variations of the filename that it can not find but it is always a 
> network path was not found.

Nancy--first and foremost, can you supply the following:
	1) version of netware (including service pack level)
	2) version of client (including service pack)

I've seen this error on very early versions of the client for
netware services, as well as some *very* specific client/OS 
combinations (specific to the type of network card in the
server).

[...]

> 
> Does anyone know if the Native32 version uses the settings in 
> config.nt 
> and autoexec.nt?
> 

We haven't had to set the files/buffers since the 95/98 days.  I
believe these are dynamically allocated in 2000/XP.

> The other part is that Netware is licensed by connection and 
> if we are 
> exceeding the number of connections, might the error look like that? 
> (Since we took out a Win98 and replaced with WinXP, would the 
> count of 
> connections increase for the XP machines, otherwise it should 
> not only 
> happen on the XP computers.)
> 

A license error would *not* look like this.  Instead, you would
never get the drive mapping.

Is the error sporadic?  If so, after it occurs, can you get
to the drive where the filePro files are stored?  (e.g., if you
have F: mapped to the server, after the error occurs, can you
still browse to the F: drive?)

Bob