WinNT--Hair on FIRE!!!! (AREV Specific)
At 12 MAR 1998 03:47:19PM Kevin Wood wrote:
This is perplexing, at least for me. Hopefully one or more of you have seen this before and can give me some guidance. One of our clients, who is running our AREV based application on a Novell 4.11 network with the 1.1 NLM, yesterday connected a WinNT server to the hub of their ethernet backbone. Within two hours many of the workstations running our application started to receive linear hash errors and disconnections. We encouraged them to unplug the newly attached NT server from their network and upon doing so we dialed in, connected to our application and it worked perfectly. It has been working fine since (without the NT server connected to the hub). Could there be some issue with the SAP address for the NLM being blocked or possible corruption of IPX packets that are in route to the workstations from the NLM? I'm reaching…
One thing I was able to find out was the person who helped them set up the NT did not have any TCP/IP protocol running on the server, only the IPX/SPX stuff and the Microsoft Client for Novell Networks along with file and print sharing. They are considering using NetBEUI and disabling all of the IPX stuff since it is not necessary for the Novell servers to "see" the NT server anyway. It seems interesting to me that they were not running TCP/IP on the server since I was under the impression that TCP/IP is NTs core protocol. I was told that they loaded the Client for Microsoft Networks on the workstations but they didn't say anything about loading TCP/IP on the workstations (and they probably didn't since they weren't running it on the server).
Does anyone have any idea what could have happened to cause LH problems? NT configuration? Novell configuration? Something? Anything? They are now looking to me for an answer since it caused problems with our application. I have added an NT server to our network and it is running in conjunction with Novell 4.11 and 1.1 NLM…no problems whatsoever. :)
TIA,
kevin
BTW, I would like to take this opportunity to thank those of you who have helped me in the past. This forum is an extremely helpful tool and my life would a lot more hectic without it! Thanks again!
Kevin Wood
Network Manager
Tri-Center Computer, Inc.
kevin@tri-center.com
At 13 MAR 1998 02:26AM ashley chapman wrote:
This could be caused by many things! But first check that you are
not accessing the Netware server using IEEE 802.3 packets.
This frame type can be easily upset by other protocols, and so
novel changed to the 802.2 format which can co-exist with IP and
NetBEUI.
At 17 MAR 1998 10:20AM D.C. @ A*STAR wrote:
If you are trying to run the NT you may need to investigate the NT service Pack. Unfortunately, we are able to run multiple protocols which all require their own little lollipops. If you are still experiencing problems, investigate the NT Servive Pack. Hope it Helps.