Discussion Locked

Reloading Netware 5.1

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My immediate supervisor thinks reloading the OS will improve things. Sometimes the system utilization jumps to 42% (dual processors) and stays there eventually causing a re-boot. I think it is corrupt files in some folders and triggers when users access them. What do you think? I need instructions for re-loading the OS the easiest less time consuming way. Thanks......

12 replies

by john.salvador

The second part is really a question : What are the instructions for re-loading Netware 5.1 on a server running Netware 5.1? Would support pack 3 be helpful? Thanks again ...

by gnet158

I had a similar problem when I was in the middle my W2K rollout last year. The server utilization would jump to 99% and then crash. In my case it was the way I was mapping drive through W2K. The way I found this out was by typing SET DSTRACE= +EMU @ the server console and looked for the connection that was causing the server to have high utilization. I then would have the user logout and the server would go back to normal. If this fits your situation then make sure your mapping your drivesthrough the little red N on the taskbar and NOT through Explore. Hope this helps.

by jimbb

There is an issue, relating to a changed way NetWare keeps track of files in use. When a workstation crashes (and which doesn't?), the files it has stay "in use", and you cannot clear the connection. You may have the same user connected several times, and none can be removed without restarting the server.
You can get around this by typing "set client file caching enabled=off" (don't forget to put this in Autoexec.ncf...).

This change came since a certain service pack in NW 5.0, don't remember which one. It is meant to prevent some abends. But this may be the result...

Jim

by jimbb

That should have been "the files it has OPEN stay 'in use'". Maybe I need another coffee ;-)

by jimbb

And if you really want to reload (which won't do much according to me), run the install program, and select the upgrade option. This way the volumes will remain untouched. You will have to select that "newer files need to be replaced" as soon as such a conflict arises, to avoid a mixture of "NetWare 5.1 files" and "Netware 5.1-with-servicepack files". Once the upgrade is done, re-apply any other installation you have done, and finish with the service pack you had installed.
But to be honest, I doubt this will solve your issue.

Jim

by jlmiller

Question that needs answering is was the utilization always high? If not then what was the last thing done on both server and workstation before the and after the utilization began to rise. If you can't answer those question (why you need to keep a server and workstation change log), then reloading the OS isn't going to help much because you are not going back to the beginning when if it's a workstation(s) that is causing this you will still have the problem. My suggestion is to get a sniffer/sniffer expert on your network and capture some packets to see what is going on. make sure you have the server patched and the workstation(s) and apps up-to-date.

by john.salvador

I love this forum. Thanks from all of you professionals. Your answers help me tremendously. All your answers are good and I only give positive feedback on those I have tested. Also, I need to conserve as many points for emergency questions. Thanks again.

This discussion is closed to new replies.