Re: Telnet Server

["Shannon O'Donnell" <shannono@xxxxxxxxxxxx>]

Hey! That works great!  I set up my proxy to run on a port, say 4055 and
then telnet from the source system to the target system, pointing to port
4055 and connect. Then I have the socket server copy the incoming data to
port 23 and I get my 5250 signon screen!  Cool!

Now I can tweak this to do the up front processing I needed as well as
attach a telnet exit program to handle the remaining special processing I
need.

Thanks all!  And special thanks to Scott Klement for the sample programs!


----- Original Message -----
From: "Chris Bipes" <chris.bipes@cross-check.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, September 04, 2001 10:58 AM
Subject: RE: Telnet Server


> You would connect to port 23 not bind to it.  At that point you are acting
> as a client, not a server.  IBM's telnet server is bound to port 23
waiting
> for your connection.
>
>
> Christopher K. Bipes   mailto:ChrisB@Cross-Check.com
> Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
> CrossCheck, Inc.   http://www.cross-check.com
> 6119 State Farm Drive   Phone: 707 586-0551 x 1102
> Rohnert Park CA  94928   Fax: 707 586-1884
>
> -----Original Message-----
> From: Shannon O'Donnell [mailto:orion@auburnctnet.com]
> Sent: Tuesday, September 04, 2001 8:19 AM
> To: midrange-l@midrange.com
> Subject: Re: Telnet Server
>
>
>
> ----- Original Message -----
> From: "Scott Klement" <klemscot@klements.com>
> To: <midrange-l@midrange.com>
> Sent: Sunday, September 02, 2001 11:10 PM
> Subject: Re: Telnet Server
>
>
> So...would I need to bind port 23 then, or could I simply write to it
> without binding it?  Seems to me that I'd get an error if I attempted to
> bind on port 23 since it's already being used by the Telnet server.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>