× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. September 2001

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


>
> I think what Mr. Ross was suggesting is that instead of calling the telnet
> server programs, you'd have your socket program receive requests on port
> XXX and then just forward the data that it receives to port 23.
>
> Basically, it'd be a simple proxy program, just copying the data from
> one socket to another, and back...
>

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.