[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== FS492 Message (AREV Specific) ====
=== At 19 NOV 2007 11:21:56AM Victor Engel wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
This morning I got an FS492 message when logging on. Poking around, I checked file handles to see if I was connecting through the NLM (I was not -- no FFFFFF in the handle after accessing the file). I checked the REVPARAM file and it was set correctly. How could this happen? I thought the whole point of the REVPARAM file was to avoid just this scenario.



I've contacted a Netware person who will be checking the server end of things. Meanwhile, what else can I look at?
</QUOTE>
----

=== At 19 NOV 2007 12:05PM Victor Engel wrote:  ===

<QUOTE>Weird. Now it's working properly. I have no idea what happened.

</QUOTE>

----

=== At 20 NOV 2007 12:00PM Warren Auyong wrote:  ===

<QUOTE>The message means that one or more of the NLM component versions (NLM, ARev Network driver, LHIPXTSR) is out of sync.



I'd suspect there is an old version of LHIPXTSR out there somewhere and the search path priority/order had gotten changed so that version was loaded.



Either that or the network protocol binding on the Novell client is set to "AUTO" instead of that of the server card setting (i.e. 802.3). When set to auto the NLM connection can randomly go out after working solidly for an indefinite time. The only way to assure this does not happen is to not use the "AUTO" setting.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=B2492EFB5DAC82E6852573980059E666|View this thread on the  forum...]]