Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!news.larc.nasa.gov!tadguy
From: tadguy@abcfd01.larc.nasa.gov (Tad Guy)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet help (please)
Message-ID: <TADGUY.91Jan6095901@abi2.larc.nasa.gov>
Date: 6 Jan 91 14:59:01 GMT
References: <1991Jan4.132514.8901@cs.wayne.edu>
Sender: news@news.larc.nasa.gov (USENET Network News)
Organization: NASA Langley Research Center, Hampton, VA
Lines: 16
In-Reply-To: jal@pandora.cs.wayne.edu's message of 4 Jan 91 13:25:14 GMT

In article <1991Jan4.132514.8901@cs.wayne.edu> jal@pandora.cs.wayne.edu (Jason Leigh) writes:
> But once connection is made I can only type but I can't see anything
> being returned to the screen.  Evidently what I type isn't correct
> either because I was expecting a certain response from a command I
> typed to the host but didn't get it.  I'm pretty sure the baud rate
> is correct.  

Your baud rate was correct until your modem issued a CONNECT message.
In your s:dnet.config file, there's a series of AUTA statements that
change the baud rate based on the CONNECT message.  The comment about
them being consulted only when the -a option is given is incorrect.

Since I only dial out, and always use the same speed, I just commented
out all the AUTA statements.  Check these statements in your s:dnet.config...

	...tad