Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!dogie.macc.wisc.edu!indri!polyslo!csun!solaria!ecphssrw@afws.csun.edu
From: ecphssrw@afws.csun.edu (Stephen Walton)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet2.0
Summary: dnet -X -h0
Keywords: HELP
Message-ID: <704@solaria.csun.edu>
Date: 9 May 89 20:30:15 GMT
References: <6974@etana.tut.fi> <3151@ritcsh.UUCP>
Sender: ecphssrw@solaria.csun.edu
Reply-To: ecphssrw@afws.csun.edu (Stephen Walton)
Organization: California State Univ., Northridge
Lines: 23
In-reply-to: franks@ritcsh.UUCP (Francis Shea)

In article <3151@ritcsh.UUCP>, franks@ritcsh (Francis Shea) writes:
>In article <6974@etana.tut.fi> mk59200@kaarne.UUCP (Kolkka Markku Olavi) writes:
>>  I can connect and login to the Sun normally through the Dnet startup
>>window, but when I try to start dnet, the Amiga side goes to a loop
>
>I also am having problems starting dnet.  I can log on to the vax but when i
>type dnet for the connection the fterm window just sits and waits.

Francis, Kolkka and anyone else who is using dnet over a
direct-connect line, as opposed to through a modem, needs to start
Dnet with the -X and -h0 switches.  -X tells Dnet that you are on a
manual connect line, and -h0 tells Dnet to ignore carrier detect.
Without -X, you'll find the remote end unable to "putfile" because the
default security level (in s:dnet.config) assumes a hostile
environment.  Without -h0, Dnet will refuse to open any servers until
it sees carrier detect, which will never happen on the three-wire line
into my office, or probably yours either.
	Matt Dillon told me all this, to give credit where it's due.
Dnet is fun, now if only I had TekTerm in addition to Fterm...
--
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
RCKG01M@CALSTATE.BITNET       ecphssrw@afws.csun.edu
swalton@solar.stanford.edu    ...!csun!afws.csun.edu!ecphssrw