Path: utzoo!attcan!uunet!steinmetz!lansoar!guilford
From: guilford@lansoar.steinmetz (jim guilford)
Newsgroups: comp.sys.amiga
Subject: Re: DNET and DECserver200 problems
Summary: I have a similar problem
Message-ID: <11468@steinmetz.ge.com>
Date: 6 Jul 88 13:20:54 GMT
References: <880705174344.04a@Ins.MRC.AdhocNet.CA>
Sender: news@steinmetz.ge.com
Reply-To: guilford@turing.cs.rpi.edu (jim guilford)
Organization: General Electric CRD, Schenectady, NY
Lines: 26

In article <880705174344.04a@Ins.MRC.AdhocNet.CA> rmf%Ins.MRC.AdhocNet.CA%Stasis.MRC.AdhocNet.CA%UNCAEDU.@CORNELLC.CCS.CORNELL.EDU.BITNET (Russ Forster) writes:
>>The problem is that the DECserver keeps seeing "Unknown characters" whenever
>>I type anything to it, so I cannot log onto UNIX.

I am having a similar problem with dnet. I am trying to talk to a unix
system running on a sun4. I am talking directly to it, not through an
intermediary.

My problem is that after logging in and "dnet"ing, I get the first
terminal window. It starts displaying stuff as it should be, but then
stops (I would get it gets one packet but no more). At this point,
dnet seems to be jammed, and all I can do is BREAK it, and try again.
It seems somehat non-deterministic, although I have had much better
success by imbedding the dnet on the unix side in a "script
/dev/null". I have no idea why this works (imbedding it in another csh
doesn't seem to help). 

I would guess that the problem is on the unix end, but I really don't
know. I would like to dnet more often, but it is a pain when I have to
fight with the system for a half-hour just to get it started. Although
once I do get it past the initial hurdle, it seems to work fine.

Anybody have an idea on what is going on or how I can fix it???

--JimG
guilford@turing.cs.rpi.edu