CONNECTIVITY ISSUE: Novell Netware 5.1 and the Revelation NLM 5.0 (Network Compatibility)
Created at 12 APR 2000 04:42PM
SYMPTOM
Revelation Software has experienced connectivity problems resulting in server communication errors with Novell Netware 5.1 and the Revelation NLM 5.0 with Advanced Revelation and OpenInsight.
If using Novell Netware 5.1 with the Revelation NLM version 5.0, Revelation NLM users will experience FS472, FS477, FS466 or FS461errors withOpenInsight and/or Advanced Revelation databases.
The symptoms being experienced with Novell Netware 5.1 are equivalent to what has been seen with Novell Netware 5.0 and Service Pack 4, with the Revelation NLM 5.0.
WORKAROUNDS
If you are considering an upgrade to Novell Netware 5.1, and are using the Revelation NLM version 5.0 with OpenInsight and/or Advanced Revelation databases, we strongly encourage deferral of the Novell Netware 5.1 upgrade. A migration to Novell Netware 5.1 with Revelation product will only result in connectivity and communication errors.
If you have already migrated to Novell Netware 5.1, and are using the Revelation NLM version 5.0 with OpenInsight and/or Advanced Revelation databases, we recommend a full and complete installation of one of the following Server and Client operating environments. Please refer to the Revelation Network Product Support Matrix for additional supported environments.
Product | Operating System Version | Client Version |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 3a | Windows 95 Client32 Version 3.1 Service Pack 2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 3a | Windows 95 Client32 Version 3.2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 3a | Windows 98 Client32 Version 3.1 Service Pack 2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 3a | Windows NT Client32 Version 4.70 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 2 | Windows 95 Client32 Version 3.1 Service Pack 2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 2 | Windows 95 Client32 Version 3.2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 2 | Windows 98 Client32 Version 3.1 Service Pack 2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 2 | Windows 98 Client32 Version 3.2 |
OpenInsight 3.7+ | Novell Netware 5.0, Service Pack 2 | Windows NT Client32 Version 4.70 |
Advanced Revelation 3.1x | Novell Netware 5.0, Service Pack 3a | Windows NT Client32 Version 4.70 |
Advanced Revelation 2.1x | Novell Netware 5.0, Service Pack 2 | Windows NT Client32 Version 4.70 |
SPECIAL NOTES If you have one of the environments above and are still experiencing problems, we recommend that you perform the following:
1. Make sure that you have forced the frame type of the IPX/SPX Protocol to the frame type of your Novell 5.0 Server. In most instances, this is Ethernet 802.2. This is done through the Network settings of the Control Panel.
2. In the Novell Client32 properties under the Preferred Protocol tab, set IPX as the preferred protocol (Win NT) or move IPX to the top of the Protocol Order (Windows 95/98).
3. Verify that the NLMs are loaded on the server. This can be done by typing modules lh* from the console. The two NLMs that you should see are LH.NLM and LHIPXSER.NLM, both of which should be version 5.0.
4. Validate that the IPX Advanced Netware Driver vs 1.5a is selected. This can be done by launching NetDrv.exe which is located in theOpenInsight directory. If you are using AREV you can do this by typing WHO at the TCL prompt (accessed by hitting F5 from within AREV). Within the WHO screen you should see IPX/Advanced Netware v1.50 next to Vendor/Type.
SOLUTION
Revelation Software has been able to replicate the problem, and a report has been submitted to Novell Engineering. Revelation will continue to work closely with Novell, so that Novell can identify a resolution as quickly as possible. We will provide more information as it becomes available.