What is the corrrect workstation Driver for NLM 5.0 (Networking Products)
At 06 MAR 2001 08:24:05PM H King wrote:
I have a client who upgraded to Netware 5.0 around May, 2000. I upgraded their NLM to the 5.0 version at that time (server & workstations). The customer is currently running support pack 5. AREV recently hangs occasionally at different workstations & I'm trying to troubleshoot why. The driver is listed as "IPX/Advanced Netware v1.5a" in the Lanpack * Network menu and when you type "who" at tcl.
When looking at the "Network Product Support Matrix" & "Benchmark Tests" documents on RevSoft's site they frequently refer to "NLM 5.0" and the "IPX/Netware Driver 5.0a". Am I running the correct driver? I don't see "IPX/Netware Driver 5.0a" on the list.
At 07 MAR 2001 01:50AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
This link refers to benchmarks with the 5.0 driver and the 5.0 NLM listed together. Usually there is an $upgrade object on the install disk which (when run from AREV) installs the correct network driver.
World Leaders in all things RevSoft
At 07 MAR 2001 10:30AM H King wrote:
Thank you very much for responding. So, do you think I'm using the right, or wrong, driver? There's nothing in the "Revelation NLM Installation Guide" telling user to run "$upgrade". I followed the procedure in the installation guide to upgrade the lan driver (page 34) for AREV 3.x. The manual tells you to pick "IPX/ADVANCED NETWARE 2.1+Drv. 1.5a" from the list.
At 07 MAR 2001 10:47AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
The documentation does indeed indicate that you are running the right driver.
When the workstations hang do they bring down other stations? Are all of the shortcuts configured as per recommendations (Suspend unchecked, max EMD set to 4096 etc etc?)
World Leaders in all things RevSoft
At 07 MAR 2001 04:56PM H King wrote:
No, when a workstation hangs is does NOT bring down other stations. I have seen subsequent users get hung trying to access an index left in use after the an initial user was hung. The initial users AREV connection must be removed for the index to be freed up.
The properties are set up according the RevSoft recommendations.
I've seen when a user gets hung and they go back into AREV the NLM-STATS utility lists them twice. The initial task never appears to get removed. This also happens when a user closes their AREV task in windows instead of exiting AREV properly.