Netware 4.11 and windows app

[Kevin]

I'm having problems with a database app (and others) running off a Netware
4.11 server that cannot be upgraded at this time. We're running IPX (802.2)
and everytime the app is opened off the server the processor pegs to 100% on
the Windows box. This happens even with rconsole and the same behavior is
observed whether the client is WinXP, Win2K or Win98.

The main app is 16-bit, so it's running in an NTVDM. I've noticed that if I
leave rconsole on the shell prompt or another screen that doesn't update
continuously the processor drops back down to normal. If I even pass the
mouse over the rconsole window, however, the winbox proc jumps back up to
100% until I move the mouse off the window again.

I have checked all the network optimization setting I know about on the NW
box and the memory and proc seems to be okay, though I really know very
little about Novell. Has anyone observed this behavior and what in the heck
can I do to fix it? The clients are all running the latest version of the
Novell client for Win.

Need more info? Just ask.

TIA,

Kevin

 

[Stephen Carter]

I'm having problems with a database app (and others) running off a Netware
4.11 server that cannot be upgraded at this time. We're running IPX (802.2)
and everytime the app is opened off the server the processor pegs to 100% on
the Windows box. This happens even with rconsole and the same behavior is
observed whether the client is WinXP, Win2K or Win98.

The main app is 16-bit, so it's running in an NTVDM. I've noticed that if I
leave rconsole on the shell prompt or another screen that doesn't update
continuously the processor drops back down to normal. If I even pass the
mouse over the rconsole window, however, the winbox proc jumps back up to
100% until I move the mouse off the window again.

I have checked all the network optimization setting I know about on the NW
box and the memory and proc seems to be okay, though I really know very
little about Novell. Has anyone observed this behavior and what in the heck
can I do to fix it? The clients are all running the latest version of the
Novell client for Win.

Need more info? Just ask.

TIA,

Kevin

If you're only attaching to NW4.X servers then make sure you install the
Novell client with the IPX only option (after selecting Custom
installation type). This will not remove TCP/IP but the Novell client
will not try IP connectivity (which if installed with IP support it will
default to every time, before trying IPX). In the client properties you
can also set a protocol preference so the client will try IPX before IP,
but I've had mixed results with this. Setting the client up for one
protocol or the other (but not both) has always given me more reliable
results.

SteveC