Hi ,

I've had this situation with win95 and Novell 6 where I get FS477 even after I have IPX as the preferred protocol. Frame type set exclusively to 802.3. Running NLM 5x.

The work around I found was to set the Arev application server as the primary server.

Anybody got any thoughts on this?

What client version on W95? Is it the MS client? Have you tried 802.2 at all?

The Sprezzatura Group

World Leaders in all things RevSoft

Hi,

Novell netware Client 3.31.0.0 and we use only 802.3 for the frame type.

Thanks

Prabir

Prabir,

Your 3.1.0.0 client is usually fine in this setting.

There are many articles on "PREFERRED SERVER" here in the forums. You might like to try this forum's "Search" feature to see what is here. Here's one I posted a couple of years ago.

http://www.revelation.com/__8525652b0066bfaf.nsf/0/eb27ca713c33de0a85256951003f8e6c?OpenDocument

Basically, when using the NLM, AREV has to see a server (across IPX) that has the NLM on it or one which will accept locks. Once the NLM is "seen" the session is established. The preferred server is set on the client, or by default is the "closest" one. If the AREV.EXE server is on a secondary server, (and Novell permits up to eight attached servers that I know of) then the workstation behaviour needs to ideally (a) authenticate on the first server (b) get a list of servers © attach each in turn & authenticate the user (d) look for the NLM on each one then (e) reset the preferred server (which could very well upset other client-based tasks) (f) map the relevant drives (g) attach to AREV using the NLM.

As there were many many problems in the Novell API in this regard (I once tried this from Assembly language objects inside AREV) the default "PREFERRED SERVER" is eminently more easy to access.

I'm not saying that this behaviour is justified, nor am I saying that this is Revelation Software's reason for omitting a network-wide multi-server search for the NLM. However, it would be plausible and quite reasonable that the amount of code required to locate the NLM on a "non-preferred" Netware server would be too great to fit neatly in 64K, and would pose serious memory and performance overheads.

My "Programmer's Guide to Netware Client API" by Charles G. Rose runs to 927 pages, so there is considerable detail involved. The reference is written for assembler programmers. Your question may seem simple. However, the answer can take some time to verify. You do have the option (for urgent issues) of raising a support incident with Revelation Software directly, at a price.

There is an old adage that as soon as any two components of your system (hardware and software) are greater than 7 years apart, you may experience difficulties. Win 95 and AREV are both 7 years old. 802.2 became the default/preferred protocol stack over 802.3 in Netware 3.12 circa 1992. Novell Netware 6 is quite recent.

I hope this adds another perspective to the system behaviour for you.

Respectfully,

Steve

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...