|
Hello Vernon, You wrote: >If you use the QIBM_QTG_DEVINIT exit point, you can know what server port >is being connected to. This way you know if telnet is not coming in to the >well-defined port for telnet. You could turn these off - there's some kind >of 'service not available' message, I think. While I think your suggestion of changing the TCP message description will probably work, I would be very surprised if the above suggestion works. The QIBM_QTG_DEVINIT exit point is a Telnet SERVER exit point invoked when a client connects to the Telnet server. It has no effect on telnet sessions to non-Telnet servers (e.g., SMPT, HTTP, etc.) because: a) The Telnet server is not involved even though a Telnet client is used. b) No AS/400 device is involved when connecting to a non-Telnet server (unless that server itself opens a virtual terminal) Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.