For a faster and stable access over WAN using AREV 2.03 application we were advised to install NLM on server. The problem is NLM does not work with Netware Client 3.21 which we were not made aware of! Is there anyone out there who may have any success or found any way around to make NLM work with client 3.21 (with the latest patch) or any other solution(we are not planning to switch to OpenInsight at this time)? Also, client 3.1 with no service pack is not a workable option for us.

Thanks to all on this board who I have found very helpful on any and all AREV questions.

S. Shavdia

We have had success in getting 3.1 (sp2) and 3.2 (I think) to work by using an older version of IPX.NLM (v2.03) which comes with 3.1 (no service packs) dated 16 Nov 1998.

Good luck.

Tim

tmarler@prosolve.co.uk @ Prosolve Software

I haven't been here in quite a while but I just got a new AMD Athlon based 1Ghz machine with Windows Me installed. It took 2 days to get the Netwares client to work then we deleted the dialup adapter and it wouldn't work any more. After about 2 more days of fiddling on and off it worked again. When we tried to get AREV to work on it we started getting the FS477 error. Tried numerous things suggested here and after doing something a second time it started working, when I rebooted the machine AREV wouldn't work again. Tried a couple of other things and all of the sudden it worked. It reminded me of something I saw here a few years ago. It help but has provided years of enjoyment as well here it is for those who want to brighten their day.

This is from Brock Prusha. Thanks Brock.

1) Make sure the network driver is IPX/Advance Netware (do a who at TCL).

2) Make sure you are loading the LHIPXTSR /P TSR before running AREV. If you are running win95 oemB, the TSR sometimes coughs when entered as a batch file in the properties box. Try loading your app with a dos batch file and loading the tsr before and unloading it after the call.

3) There is an option on the TSR to indicate how long to wait before timing out. I think it's /C:120 or something, but don't hold me to that. Check the manual.

4) Make sure the IPX/SPX protocol in win95 is set to the frame type instead of AUTO.

5) Tell the nlm what the frame size in when loading it on the server.

6) There is no number six!

7) Increase the number of sockets on the workstation.

8) Dance in circles while sacrificing a chicken to the techi god and pray s/he's in a favorable mood.

9) Make sure the REVPARAM file is setup with ServerOnly=1 in each arev directory.

10) Use NLM_STATS in arev to double check that it is talking to the NLM, if ya can get in that is.

10) Try reinstalling it and making sure it is serialized properly.

Good luck!

Brock Prusha

DFM Systems, Inc

bprusha@mapcon.com

Can you explain this further? Which IPX.nlm are you referring to… ? Are you running 4.11 or 5.1 We're running Netware 5.1 server that doesn't load IPX.nlm..only IPXS.nlm.

I'd like to update the the Netware client above 3.10 (no service pack). Ideally, Netware 3.21.

Suggestions?

View this thread on the forum...