Debug Errors when logging onto OI 3.5 (OpenInsight 16-Bit Specific)
At 11 JUN 2003 09:19:03AM Matthew Mahon wrote:
Good Morning…
We have recently implemented Revelation NLM 5.5 for our OI3.5 users. Since utilizing the NLM, my users are encountering numerous debug errors both while trying to log into the OI app and while actively working within the application itself. I was told this is normally called by network mismatches. The errors being generated are sys1000, rpt037, rpt036, repos_bfs–fs481, repos_bfs–fs472, etc. I have set all devices to Auto Detect for speed and duplexing. Had the server set to Auto Detect and verified that all ports on the switches maintained the same information. Also set the frame type to be 802.2. Regardless of the attempts I've made, the problem with these debug and access issues keep popping up. Can anyone assist me with identifying other areas of concern that I have not tried yet???
Thank you,
Matthew Mahon
At 11 JUN 2003 09:40AM Don Miller - C3 Inc. wrote:
Sometimes setting the Auto-Detect on causes problems. I usually specify the desired frame type. What desktop version of Windows, Network Client Version are you using. The NLM seems to be much fussier about connectivity issues. There are a couple of FAQ's available that detail the current supported versions. Releases of OI prior to 3.7 also had some connectivity issues with the NLM.
Don M.
At 11 JUN 2003 10:06AM Matthew Mahon wrote:
All devices are running Windows 2000 with v4.83 SP1 Novell Client. Its funny…our policy was to set all devices/switches to 100/Full, but that has since changed so we went back and changed it to AutoDetect.
At 11 JUN 2003 11:10AM Matthew Mahon wrote:
….but this problem was not generated by the change in speed/duplexing. That occurred before we obtained the NLM and attempted to place it into production. You mentioned something about a FAQ. Where can I find that section???