>>SNIP
>>>
>>>Nope, Cetin, you're not alone. The one thing that I particularly hate is that Novell 4.x/Client 32 is agressive to the point of being obnoxious. Never mind what you want your DOS path setting to be, Novell will merrily reset it for you without warning, and without (apparently) the ability to either disable it or override it. And to think we're "upgrading" (there's a euphemism for you) all our servers to it. Groan...
>>
>>Well, Maybe it's just me but once we applied all the patchs to Netware 4.1 and Client 32 we are screaming along. We get better performance off of are Netware 4.1 server than we do on our NT 4.0 server (Identical Hardware). Granted, it took some playing with the Client32 settings and applying all of the patches (Like Microsoft doesn't have any) to get to a stable point. I also think Netware 3.12 was a better NOS but no longer an option for us.
>>
>>IMHO as always.
>
>If you can give me any information about what Client32 settings you tweaked, I would appreciate it. I found something about the AutoReconnect Level and changed that on a test machine here. We got better response and thought we had it licked until the software was placed on-site and the problem popped up again.
>
>Thanks,
>
>Wayne

Wayne,
In our setup we do not allow Client32 to auto select anything. We set the frame type, Speed and Duplex mode. IPX/SPX is our default protocol (NetBios is enabled over IPX/SPX) and TCPIP is the only other protocol loaded. We also disable source routing. Some of our settings are driven by software we must support across the network.

Applying all of the Netware patches went along way to increasing speed and reliability. I can't remember that last server crash that could not be traced to a user (or Network Admin) doing something stupid. But a plug for Netware 3.12, I had a server up for 768 days before we took it down to upgrade the memory (up to 64 Megs) and add an additional hard disk (Up to 4 GIG). Those were the days (only 2 years ago).

Hope this helps.