Windows 2000 Client & Arev (Networking Products)
At 23 MAR 2001 08:07:38AM k prociou wrote:
Our configuration is Arev 2.12, Novell 3.2 NLM 1.5
Installed a Windows 2000 workstartion with Novell client 4.8.
Has there been any resolution to the problem of AREV running extremely slow when running Windows 2000 desktop.
Thanks
At 23 MAR 2001 09:38AM Mike Ruane wrote:
K-
We've re-opened the incident with Novell. Right now, most of Novell's developers are at a conference, but as soon as they return we'll get back into this with all our resources.
As soon as we have a resolution we'll make a posting here.
Thanks-
Mike Ruane
At 03 APR 2001 12:14PM Chris Cordera wrote:
Mike
I have done quite a bit of testing with AREV 2.12 on Win2k and have concluded that the culprit is not the Novell Client. I removed it and installed the MS Client for Netware with no difference in performance. It may be the combination of AREV/Win2k/Netware as I have not tested AREV/Win2k/MS Network. This is on Dell Dimension 8100s with P4 1 Gig processors and 500MB RAM on a small 100MB LAN using the LH NLM. These machines smoke all other applications yet AREV runs like molasses.
On the same LAN, an NT 4 machine running a Pentium Pro 200MHZ runs AREV just fine. I wonder what changed with Win2k since it is really NT 5. Looking at the task manager the AREV VDM gets starved for CPU cycles often getting 0% even when running a routine in foreground. I have tried adjusting the shortcut and tweaking the process priority in the Task Manager with no luck.
If you have any other tweaks please let me know.
Thanks
Chris
At 04 APR 2001 12:47PM Dan Reese wrote:
I too have done a lot of testing. The problem does not appear to be as simple as Windows 2000 on NetWare.
If you unload the NLM and use the All Networks driver, Windows 2000 performance increases about 4 fold on our benchmarks on a Novell 4.11 IPX/SPX-only network. This means that, on some level, Windows 2000 can use IPX to communicate with a Novell server at a much higher speed than we are seeing with the NLM.
Therefore, problem appears to be some sort of interaction between LHIPXTSR, the NWLINK program (Microsoft's implementation of IPX), and the Revelation NLM.
At 04 APR 2001 02:16PM Mike Ruane wrote:
I perhaps oversimplified.
It appears that in the configuration I mentioned (Win2k ws to Novell) that there is some change in the packet broadcast scheme that drastically slows down our performance.
It also happens with OI, which eliminates the TSR.
We're trying to work with Novell on this, which is a sometimes trying process.
Mike