[[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]]


==== Novell Client32 and NLM 1.5 (Networking Products) ====
=== At 24 MAY 1999 04:00:40PM John Bouley wrote: ===
 
{{tag>"Networking Products"}}
 
<QUOTE>
I saw a message from Revelation Software back on November 98 talking about problems with Client 32 2.5.

First, was there any resolution to this problem.

Second, the current release of Client 32 is 3.1. Will this work correctly with the NLM. If so then are there any settings that need to be changed? 



Thank You.

John Bouley
</QUOTE>
----

=== At 24 MAY 1999 04:34PM Stephen Revelation wrote:  ===

<QUOTE>John,



The resolution we came up with to the Client32 v.2.5 problem was to set extended memory equal to none in ARev's (shortcut) memory settings.  This also fixed a similar problem with Client32 v.3.0.1.  



There are no known problems related to Client32 v.3.1.0 that we have experienced with our NLM's.  I would recommend forcing the frametypes on your IPX/SPX and IPX-32-bit protocol settings to match that of your Novell server however, instead of letting Windows auto-detect them.



Regards,



Stephen Revelation

</QUOTE>

----

=== At 24 MAY 1999 05:39PM Matt Crozier wrote:  ===

<QUOTE>John,



Is there any explaination for the behaviour of Client32 3.10 in [url=http://www.revelation.com/WEBSITE/DISCUSS.NSF/f12696d31000b22a8525652b00831bb2/5d8340b8d6974f7e8525677800749b62?OpenDocument]this situation[/url]?  We would like to tell our clients to upgrade their Client32 but would like to see some response to this query first.



Thanks,

Matt.

</QUOTE>

----

=== At 25 MAY 1999 08:18AM John Bouley wrote:  ===

<QUOTE>Matt,



I have not tried using Client32 3.1 yet on a Novell Server. The only suggestion I have for your problem would be to make sure the frame type matches the frame type of your server and the protocol search order has IPX first instead of IP. Maybee this will fix your problem? Please let me know because I have several customers who are in the process of upgrading clients for Y2K reasons.



Thanks,

John Bouley

</QUOTE>

----

=== At 25 MAY 1999 12:47PM dave santos wrote:  ===

<QUOTE>Hard setting the protocol to 802.2 and making sure I had the right nwcalls.dll and nwipxspx.dll seems to have done the trick for 3.1



Still stuck in the mud with citrix.....or accessing from any NT Workstation for that matter.

</QUOTE>

----

=== At 02 JUN 1999 12:51PM David Salvesen wrote:  ===

<QUOTE>We too have customers with problems with the Novell Clients and particularly with NT4 workstation. 2.5 for 95/98 does seem to be very ropey and when I tried 3.1 it slowed down screen refresh on my computer no end (lots of disk access whilst drawing up things like Word and Pegasus). I therefore went back to version 2.2.



RevSoft did suggest (over here) that the Microsoft client did not have problems on NT4 or that it should be installed before the Novell client. Also what are the correct versions of nwcalls.dll and nwipxspx.dll mentioned earlier?



Any thoughts about getting NT4 workstation going would be greatfully received as I have a customer who has been stuck for some months now unable to get the client going.





</QUOTE>


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