× 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.


  • Subject: RE: Change telnet to another port?
  • From: Roland Harris <Roland.Harris@xxxxxxxxxxxxxx>
  • Date: 04 Feb 2000 14:28:09 +0100
  • Alternate-Recipient: Allowed
  • Conversion: Allowed
  • Disclose-Recipients: Prohibited
  • Original-Encoded-Information-Types: IA5-Text
  • X400-Content-Type: P2-1988 ( 22 )
  • X400-MTS-Identifier: [/c=NL/admd=400net/prmd=ABNAMRO/; 037DE389AD3E92F4-abnamronlp01]
  • X400-Originator: Roland.Harris@nl.abnamro.com
  • X400-Received: by mta aabMTA-nlp01 in /c=NL/admd=400net/prmd=ABNAMRO/; Relayed; 04 Feb 2000 14:28:09 +0100
  • X400-Received: by /c=NL/admd=400net/prmd=ABNAMRO/; Relayed; 04 Feb 2000 14:28:09 +0100
  • X400-Recipients: non-disclosure;

This will work if you follow the below process AND as per Jeffreys 
earlier memo,
ensure you have ptf SF53489 (for V4R3) or supercede (now SF60463) and 
follow the cover 
letter instructions to  CALL PGM(QTCP/QTGSRV) PARM(*PORT).

Until you call the program and stop/start your telnet server, telnet will 
still listen on port 23, 
after calling program, the port number you define in your service table 
will be used. 

On V4R4 all should work succesfully without any PTFs or programs.

Roland

---------------------- Forwarded by Roland Harris/NL/ABNAMRO/NL on 
04/02/2000 14:14 ---------------------------


rpg@cross-check.com on 04/02/2000 01:08:00
To:     MIDRANGE-L@midrange.com
cc:      (bcc: Roland Harris/NL/ABNAMRO/NL)
Subject:        RE: Change telnet to another port?

Tried that.  So far as to IPL the 170 after changing the service table.
Telnet server still was listening at port 23.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   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

*Note to Recruiters
Neither I, nor anyone that I know of, is interested in any new and/or
exciting positions. Please do not contact me.


-----Original Message-----
From: Chad S. Lauritsen [mailto:csl@plconline.com]
Sent: Thursday, February 03, 2000 12:44 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Change telnet to another port?


it would probably be easier to ask the provider to use a different 
port...I
have
been looking thru the CFGTCP command on the 400,
if you do a '21' (work w/ related tables) and go to '1' (work with service
table
entries) you *may* be able to change the telnet for tcp and udp protos to
something other than 23...then hopefully by restarting the telnet server, 
it
would bind to the new port specified in the services table. There didn't
appear
to be any way to configure the telnet server/daemon using 'Configure
applications' under the CFGTCP menus. If the telnet daemon on the as/400
does
something similar to getprotobyname() as a UNIX host ostensibly would,
changing
the value in the services table should suffice to get the as/400 telnet
server
to listen/bind to a different port.

As for client access, I did a quick look and i didn't see any obvious way 
to
connect to a user-specified port. perhaps there is some registry hacking
that
could enable this? Maybe I just missed it. One would think there *must* 
be a
way!



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.