From Adrian Maggs · 1996-04-10 17:52 · #65318 in AMIGA.EUR
In reply to Terminal program with telnet? by John Marchant
Hi John,
In a message dated 07 Apr 96 you wrote to me:
AM>> It's on aminet as telser130.lha, in comm/tcp.
JM> Thanks. I'd found and downloaded Telser, but I'm still baffled. Does
JM> this mean I have to connect to my ISP using the comms terminal program?
No. Connect to your ISP as normal. (If fact telser needs a TCP stack to
work).
JM> I'm not too happy about this. Surely AmiTCP and cslip etc all have to
JM> be started first? Normally I run a dialup script which then runs a
JM> connect script to start everything, and I'm ready to run telnet, ftp,
JM> whatever.
That's fine, just contiune to do this.
JM> The "standard AT commands" can dial the ISP yes, but how does one then
JM> get TCP and cslip running? Or if I've already established a
JM> connection, then the AT commands are redundant.
Sorry, perhaps I didn't make myself clear.
Once you've got your connection established with your ISP, using your normal
method, and AmiTCP is up and running, you can then start NComm etc, with the
telser.device selected instead of the normal serial device.
To actually connect to a telnet host, all you need to type is
ATDT telnet.host.name
you can, of course, save your most used hosts to a phonebook.
The guide file that comes with telser gives all the various commands you
can use.
// Adrian FidoNet 2:2500/179.8 *Member:* *Team* *AMIGA.*
\X/ Internet adrian@uacomm.demon.co.uk
PGP 2.6ui key available - Email mailserver@uacomm.demon.co.uk
--- Mail Manager 1.1x/p
* Origin: Down the M5 from QDX! (2:2500/179.8)