[Coco] Network Access for my COCO

[Aaron Wolfe]

Yes, the port *must* be the port that the BBS you are trying to
connect to listens on.  It's just as important as the IP address.
Without having that right, you'll never get connected... you cannot
just make them up :)
All listings for telnet BBSes will include both the IP address and the
port to use.


On Sat, Jan 4, 2014 at 9:50 PM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> Aaron, ok, I tried typing the cmds directly into supercomm and it get's me "NO CARRIER" on supercomm and "while making outgoing vmodem connection: Connection refused: connect"
>
> This was using ADT71.68.29.241:65512
> ATZ & ATE1 give me ERROR in supercomm
>
> Should the port be anything specific? I just used the next available port number from what I'm using with my TCP connections (65504/65505, 65506/65507, 65508/65509, 65510/65511).
>
> What am I doing wrong?
>
> Bill Pierce
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Webmaster of The TRS-80 Color Computer Archive
> http://www.colorcomputerarchive.com/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Aaron Wolfe <aawolfe at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Sat, Jan 4, 2014 9:18 pm
> Subject: Re: [Coco] Network Access for my COCO
>
>
> the auto dialer may be mangling the "number".
>
> try just typing:
>
> ATD1.2.3.4:5678
>
> (with the correct IP address and port).
>
> The modems start out in echo off mode, if you prefer to see what
> you're typing you can do 'ATZ' or ATE1 (i think) or any other command
> that toggles echo first.
>
>
> On Sat, Jan 4, 2014 at 9:14 PM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>>
>> Aaron,
>>  I tried accessing Bill Gordon's online BBS with the Coco 3, NitrOS9 3.2.9,
> DW4 running SuperComm. I put the address in the autodialer as you said. It just
> dials and redails over and over. The Dw4 console show's connection refused. The
> BBS is active as I can log on with my browser.
>>
>> Any ideas?
>>
>> Bill Pierce
>> My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> https://sites.google.com/site/dabarnstudio/
>> Co-Webmaster of The TRS-80 Color Computer Archive
>> http://www.colorcomputerarchive.com/
>> Co-Contributor, Co-Editor for CocoPedia
>> http://www.cocopedia.com/wiki/index.php/Main_Page
>> E-Mail: ooogalapasooo at aol.com
>>
>>
>>
>>
>> -----Original Message-----
>> From: Aaron Wolfe <aawolfe at gmail.com>
>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>> Sent: Sat, Jan 4, 2014 8:26 pm
>> Subject: Re: [Coco] Network Access for my COCO
>>
>>
>> Documentation of the networking functions is available on the main
>> documentation wiki:
>>
>> http://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title=Using_DriveWire#Ports
>>
>> You do not need to make any changes to config.xml to use inetd.
>>
>> You may need to set a TermPort value if you want to use headless, or
>> there may be one set already, just depends on how long ago you
>> installed DW I think.  This would be the only setting needed on the
>> server side for networking in any case, and again it is only required
>> for headless mode.
>>
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco