file access times out

March 21, 2011 at 09:39:06
Specs: Windows 7
I have a novell client 4.91 SP5 installed on a Winows XP SP3. Files on the mapped volume are migrated from a linux box, we have a backup product. When I try to access the migrated files (copying them from one location to another), the recall kicks in on the Linux box and I can see the data from media is getting written to the disk (this is a backup/archive product), but before the recall could finish the copy on Novell Client times out with "no network connection" error.
Any connection parameter that's affecting it?
If I try access the file on the Linux box (by physically accessing the migrated file, via cat), I dont get any error and the I get the file recalled intact from media.

See More: file access times out

Report •

#1
March 21, 2011 at 12:44:31
Try the following:
In Novell Client / Advanced Settings, switch "File caching" to off

At the netware server console, type in:
set client file caching enabled=off
set level 2 oplocks enabled=off

This settings should take effect without restarting the server.
To make this settings permanently even on server restart, put these two settings in the startup.ncf file on C:\NWSERVER\STARTUP.NCF

Report back.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#2
March 22, 2011 at 11:52:54
No this does not help. This a OES linux box. I did set OPLOCK_SUPPORT_LEVEL to 0 using ncpcon and tried it again, but to no avail. Copy is aborting with error, and then then entire mapped drive is unaccessible with network error, until I do a "rcndsd restart".

Report •

#3
March 22, 2011 at 19:20:11
Die you get this error on copying files greater 2GB or did you get it during copying a bunch of short files?

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
March 23, 2011 at 08:23:45
it's also noticed that with the same netware client and same files and same backup product, it works fine if the files are on a Netware server (6.5) rather than on OES.

Report •

#5
March 23, 2011 at 08:26:15
I did try with a single big file, simulating the recalls to make them slower on the OES server anticipating a copy error.

Report •

#6
March 23, 2011 at 14:09:46
Which backup product are you using?
What did you find in the FAQ of the backup product manufacturers home page about that product in conjunction with Novell OES server?

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#7
March 23, 2011 at 14:39:01
CommVault File Archiver, I dont actually see an issue with the product, since I can very much recall the archived file by physically accessing it from the OES box, but I cant do the same by accessing it via novell client sitting on some windows XP box.

Report •

#8
March 23, 2011 at 16:44:14
Just to clarify, are you trying to access the archive files from the windows xp box or did you access the original files on the OES server from the xp box?

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#9
March 23, 2011 at 18:43:18
original files on the OES box using the novell client from the windows XP box.

If i directly try to access the archive files on the OES box (via cat or file command), the recall is triggered and i get all the file data recalled back from the media, intact.
If I access the same files from Windows box using Novell Client (copy the file from one location to another), still the recall that is triggered on the OES server finishes successfully and gets me all the data from media correctly, but by this time the copy operation which had originally accessed the file on Windows box via novell client has timed out.

There is one factor, the recall that is triggered on the OES server does not let the user I/O go ahead until all the file data has come back from media and written to disk (there is no staging file in between). Could this be a factor, if the Novell Client requesting the file from network expects the data to come in chunks or pages?


Report •

#10
March 23, 2011 at 19:25:12
Novell Client uses NCP (NetWare Core Protocol), to access file, print and directory (means NDS, eDirectory) on the server.
The port number used by NCP is TCP/UDP port 524.
With burst mode enabled, the frame of paket, being transfered without another request is 64kB.

So the files will be transfered in max. 64kB chunks.
When I remember correctly, the default frame length is 576 bytes, without burst mode enabled.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#11
March 23, 2011 at 20:33:26
Is there any time for which the novell client will wait after it requested a file on the network before it announces network resource to be unavailable?
As it seems to me that since the driver on the OES server does not let the server transfer any data to the client until all of the 750MB (could be more) of data has been received from media and written to the disk (this process can take long), the client could be thinking the resource is not available?
In simple terms, what happens if he client doesn't receive any data from the server? Will it wait forever? Will it time out ?


Report •

#12
March 23, 2011 at 21:28:56
It will time out.

Anyway, have you checked the Novell Client settings?
Especially the "Advanced Settings", "File Caching" should be set to off and "File Commit" should also be set to off.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#13
March 24, 2011 at 06:26:32
Yes both of these values are set to OFF. But it does not seem the client issue any more either, since the same novell client from same windows XP box can access same set of file sitting on a netware 6.5 box rather than a OES box. So it seems to me mostly that protocol between NCP and the client is defined in a way which does not tolerate this much delay in receiving the file data after it has been requested by the client from the server. I dont see any setting affecting it too.

Report •

#14
March 24, 2011 at 06:38:55
I think, what we should be looking for is, is there any keep alive mechanism between the NCP server and the Novell Client.

Report •

#15
March 24, 2011 at 08:04:52
A quick search in goolge for:
novell client ncp keep alive

showed this:

http://www.novell.com/support/viewC...

Maybe that helps.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#16
May 9, 2011 at 14:50:22
Did you have any resolution to this issue. We completley have the same deal with Commvault Archiver.

Report •

Ask Question