Re: Telnet Server

My idea of connecting telnet to two different ports was based on the idea
that if I had folks coming in on a port other than standard, then I would
know to call a specific program and do something.

This was the best I could come up with prior to hearing from many of you
that I could just redirect the output from one port to another using a
socket server. I like this latter idea much better and it's sure a lot more
straightforward to understand.

Thanks all for the feedback!  I'll let you know how it works out.

Oh...and a dumb terminal that is connected to an as/400 via twinax can use
telnet to pass through to another tcp/ip connected system. So the answer to
"Do dumb terminals use the telnet server?" is, sometimes.

----- Original Message -----
From: "John Ross" <jross-ml@netshare400.com>
To: <midrange-l@midrange.com>
Sent: Sunday, September 02, 2001 10:34 PM
Subject: Re: Telnet Server


> I maybe confused but I thought you wanted to connect to two different
ports
> and do telnet, and if it was on one of the ports do something special. And
> I thought the problem was you could not start telnet on two different
> ports. With the socket program you could bind on a port of your choice as
> long as it is unused. Here is what I was thinking. You would leave telnet
> running on its normal port. your socket program would run on some other
> port. You would move your exit program logic into your socket program,
then
> your socket program would pass the data out to the telnet server. That is
> what a proxy server program does, takes data in, maybe a little checking
of
> the data, and then passes it along. Since I do not know what you are doing
> in the exit program I may not be seeing the problem.
>
> Here is another thought, instead of port how about two IP addresses?
>
> And do dumb terminals use the telnet server?
>
> John Ross
>
>