|
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! it is worth noting that the as/400 telnet client, when prompted and showing all parameters, will enable the use of a user-specified port to connect to. as for other clients, it just depends on whether the programmer(s) enabled another port to connect to. if your provider is nice, they may accommodate you by switching to some other port. :-) +--- | 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 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.