15 replies
by magetower
by stillatit
Is the server a bit underpowered? It may be that the server is so busy doing the Ncopy that it is not getting around to responding to the heartbeat signals from workstations. If a workstation and server do not get each other's heartbeats, the connection goes down.
If this is what is happening, a solution is to do the copies in some other way, so that the cpu is not maxed out.
Good luck.
Happened to me too.
I had to reorganize the whole folder (adding subfolders, put the appropiate files in them , etc) and then copy it like that), there were thousand of files in that folder.
In my case I was able to zipped the files also afterwards, since they were only periodically used.
Don't know the cause of this yet, but right now it's only maintenance keeping.
by kelly_aitch
Check this out: http://support.novell.com/cgi-bin/search/searchtid.cgi?/10022150.htm
The cause is: "Net Status Busy Timeout" mechanism gives up on server connection because of a non-completed NCP operation. (so there!)
The TID gives a couple of work-arounds that I wish I'd have know about a couple of years ago when struggling to copy data to a new larger drive. I got all the data over except for a half dozen humongous files (200 MB +) that would crap out in this way.
Cheers
by duster52
Just curious....have you tried using a straight DOS copy or xcopy? Have you tried to copy through Explorer?
How many total files are you copying? There is an upper limit (I think around 10,000) of files in a directory that can cause problems like this.
Also check your Directory Cache Buffers on the server. If you reach your max setting then clients will be affected and loss their connections (I've experienced this).....it also happens when you make large changes to file rights and you are at your max setting.
by craig haunch
I do not agree with any of the previous answers.
No matter if it is the same server or not, the problem is how netware works!. The major problem is that netware, believe it or not!, is not multi-thread. Netware will try to "finish" the copy (thread) before paying attention to another tasks (threads). There's no TIME routine for threads executions. That?s why some wks may loose it's connection to the server. More longer files causes more loose connections.
Recommended actions:
Install spack 7a
Set client presist connection to a higer value
Have ipx/spx installed and working
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending