Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!clarkson!news.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Network connection hangs up with BYU/Novell/CUTCP Message-ID: Date: 6 Nov 90 06:34:22 GMT References: <657839430@lear.cs.duke.edu> Sender: news@news.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Distribution: na Organization: Clarkson University, Potsdam NY Lines: 21 In-Reply-To: djc@duke.cs.duke.edu's message of 5 Nov 90 21:10:31 GMT Nntp-Posting-Host: image.soe.clarkson.edu In article <657839430@lear.cs.duke.edu> djc@duke.cs.duke.edu (David J. Cherveny) writes: We've been using BYU's version 2.01 Novell to packet driver interface, version 7 packet drivers ( ni5210 ) and Clarkson's version of telnet, CUTCP. It works most of the time be we occasionally have the workstation go read with a network connection message from Novell: It sounds like the packet driver and/or the card is getting confused. It's the packet driver. There's a note in read.me about it. You need to reassemble the packet driver with DAN EQU 0. I don't know exactly what the problem is, but it doesn't appear on all ni5210's, just some. I'm working with someone to find the problem. If anyone else would like to help, send me mail. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.