Discussion Locked

Help with big probs - Win2000+Netware?

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My company has about 100 pc's with a Novell 5.1 server. We?ve only used Win9X on desktops and I just convinced my boss to let me set up a W2K pc with our software (Office97, Timberline, etc.) It seemed OK at first. Then some Word docs (with HTML) and Access .mdb?s would lock up, and I had to Ctrl-Alt-Del to end them. That was the start of the real problems. Whenever I?d login on the W2K pc, I?d get a login session listed on the NetWare server monitor that wouldn't release even after powering the pc down. After a few reboots we?d have up to 6 connections listed. This was discovered at the server restoring a backup of the .doc and .mdb files W2K trashed. It trashed the files so bad (really just "locked" them, I guess) that if you tried to open them on another pc, it would lock up as well. The W2K connections listed on the server were so locked that you couldn't even end them manually from the server AND we couldn't even manually "down" the server without it hanging and we had to powerit off. This happened twice. We yanked the CAT5 out of the W2K pc at that point.
I'll also note that the Novell login on the W2K pc was with my normal existing account while logged in with it on my regular station at the same time (switching back and forth with a switch box). I also rebuilt the W2K OS and installed Client32 in more than one way so far (from the W2K client offered in the setup and Client32 v.4.8 from Novell's website). Lastly, we read about the necessity of installing W2K's service pack 1...which the CD case said this W2K CD has...but I haven't confirmed that this SP1 is in the setup itself already and not a separate .exe on the CD. So far, we can't see using W2K at all, unless we can fix these problems. Any suggestions?

11 replies

by bart777

We have been running many Win2K machines on our Novell network for over a year. I remember having some prolems like this early on.

A couple of things to try;

First, remove the client. (If you can do it, either hack all of the items referring to the client out of ther registry or rebuild the system from scratch.)

Then reinstall a custom setup. Only include those items that you will need. Try to avoid installing Workstation Manager (We call it Mangler). This has helped to resolve many of our headaches. Also the imager can cause problems.

Hope this helps, As I say it worked for us.

Best of Luck.

by teddyrux

Just as a side note: run winver.exe on the Win2K machine to determine what service pack level it is.

by na_paul

Just a few comments, beginning with: follow the recommendations of the previous answers. When first deploying W2K last year I also ended up installing the Novell client as a custom setup without any options - such as Workstation Manager - which cleared up a lot of initial problems.
I also wanted to let you know that we are successfully running Timberline (was 5.4, jsut upgraded to 7.3.2) from our Novell server on W2K clients. I was even able to set up a software package to deploy the Timberline client software using Active Directory (we also have a W2K server inaddition to Netware).

by markwoo1969

We've been using the NetWare client v4.71 with NT and W2K. One very important setting change to make is in the NetWare Client Advanced Settings tab. Change File Caching from On to Off. This setting is called Opportunistic Locking in client versions previous to 4.71. This cleared up problems we had that were similar to what you described.

You should also make that change on 95/98 and NT clients as well.

We also have installed the Workstation Manager to prepare for using Zenworks - havehad no problems with it. In fact, some people like it better than the scheduler that comes with Windows.

We have also implemented W2K IP only; not using IPX on these PCs at all. Logins are cleaner and faster. All our servers continue to run IPX and IP but we're moving to a pure IP environment and are trying to move away from IPX on the PC and printing side. Make sure SLP is setup correctly on the servers and you should be okay.

by trzuskotm

Firts I would try increasing the file locking on the server in 'server parameters' in monitor on Netware 5.1. In addition to this, the file caching on the novell client running on windows 2000 should also be turned off. These two procedures that Ihave just mentioned should resolve your file locking.

This discussion is closed to new replies.