Show pageOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== Connectivity Issue: Novell 5.0 Service Pack 4 and Revelation NLM 5.0 (Network Compatibility) ====== ====== ====== ==== Created at 11 FEB 2000 04:05PM ==== **SYMPTOM** ** ** Revelation Software has experienced connectivity problems resulting in server communication errors with Novell 5.0 Service Pack 4 and the Revelation NLM 5.0 with Advanced Revelation and OpenInsight. If using Novell 5.0 and Service Pack 4 with the Revelation NLM version 5.0, Revelation NLM users could experience FS472, FS466 or FS461errors withOpenInsight and Advanced Revelation databases. **WORKAROUNDS** ** ** |**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 frametype of the IPX/SPX Protocol to the frametype 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 the OpenInsightdirectory. 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. **STATUS** ** ** Novell has verified that the getInternetAddress call was broken in Novell 5.0 SP4 and subsequent releases (i.e., Novell 5.1). Revelation has received a beta copy of the fix to the CLIB.NLM that addresses the getInternetAddress call problem. Revelation testing has determined that it resolves the connectivity issue. **PERMANENT** **SOLUTION (updated May 25, 2000)** ** ** Novell has informed Revelation Software that the updated CLIB will be included in a Support Pack for NetWare 5.0 and 5.1. Novell has provided a preliminary release date of May 31st for the Support Packs. Novell will notify us if this date changes and will also provide us with the appropriate filenames for download from their site when they become available. The Novell incident number is 2366108. kb/kb_articles/kb0185.txt Last modified: 2024/01/30 13:36by 127.0.0.1