NLM 5.5 Version conflicts (???) (Networking Products)
At 21 MAY 2003 02:24:42AM Andrew Wiley wrote:
Hi
We are in the process of upgrading our server to Netware 5, and have purchased the NLM 5.5 upgrade.
After performing both the client and server upgrades what seemed successfully, when loading the NLM on the workstation before running our application it says Revelation TSR Version 1.12!
We checked the server for the version of the NLM installed and it says 5.00!? The disks are definitely labelled NLM 5.5. Date stamps on the files on the server disks are March 1999? Do we have the right disks..??
Is there something else we need to do for the workstation to recognise the 'new' NLM version or do we have the wrong disks to start off with!?
Also, we were previously running successfully on our old server with frame type Ethernet II - it says in the Installation manual that Ethernet 802.2 must be used? Is this correct or is it ok to use either as long as client and server use the same?
Thanks!!!
At 21 MAY 2003 02:51AM Andrew Wiley wrote:
Sorry, i forgot to add, when starting the NLM on the workstation and then trying to run the application - get error FS60417 (which i have read on here may be something to do with version conflicts?!)
App starts fine without loading NLM first.
Thanks
At 21 MAY 2003 07:14AM Don Miller - C3 Inc. wrote:
Andrew:
]]Sorry, i forgot to add, when starting the NLM on the workstation ]]and then trying to run the application - get error FS60417 (which i ]]have read on here may be something to do with version conflicts?!)
]]App starts fine without loading NLM first.
Well, something is VERY wrong, then. If you don't load the NLM on the server, then you shouldn't be able to start the if the REVPARAM file specifies ServerOnly=1. So, if you don't have a REVPARAM file set this way (which is not a good idea) then that would explain it. If you load LHIPXTSR before AREV, and the NLM is not loaded, then it will crash and burn. I would suggest that the spec for Ethernet Frame type be followed. I've seen problems with many networks when it isn't (particularly in a "mixed client" installation - Win9x, Win2K, WinXP). The NLM is very particular about the transport layer and server to desktop connectivity. If you search the forum you will find a great deal of information on this topic.
Don M.
At 21 MAY 2003 07:36AM Kevin Revelation wrote:
Andrew,
Yes, something is wrong. The Server disk is correct in stating that it is 5.0. The TSR from the client side, though should not be 1.1x. After you installed the Client side driver (with the AREV INSTALL command), did you select the driver from the driver list (with either AREV BUMP or AREV LANPACK depending on your version of Arev)?
I have seen better results using 802.2, but there are sites that still use Ethernet II.
Still, taking care of the client side is the first step. If you are still having trouble, feel free to contact me at kevin@revelation.com
Hope it helps.
Kevin
At 10 JUL 2003 10:57PM Andrew Wiley wrote:
Update:
We finally got NLM 5.5 working by swapping the frame type on the client and server from Ethernet_II to 802.2. While Ethernet_II works OK with NLM 1.5 it doesn't appear to work with NLM 5.5
Andrew