Home > IT Answers > AS/400 > Telnet User Exit Program
Help

Question

  Asked: Jun 6 2008   3:50 PM GMT
  Asked by: Piano

Telnet User Exit Program


Client Access, User Exit Program TELNET, TELNET, TELNET exit programs

Hello Everyone

Does anyone know how to prevent a Telnet User Exit Program from affecting Client Access.
I am able to block a user from getting in thru telnet xxx.xx.xxxx from the PC side.
Yet, this same exit program also blocks a person from using client access, which I can not have.

I don't really understand what my issue is, or, maybe it just isn't possible to affect the PC telnet command, without affecting the Client Access command.

Bottom line is that I don't even want my exit program to run, insofar as Client Access is concerned. Only when telnetting in from the PC Telnet Command.

Please advise

Nick

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window
Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER
View History
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
Last Answered: Jun 9 2008  11:31 AM GMT  by Gilly400





Hi Nick,

Wouldn't it be easier to remove the telnet program or access to it from the PC's? I suspect that client access uses the same protocol and ports as the regular telnet program, so it's going to be difficult to work out which program is being used by the PC.

Regards,

Martin Gilbert.
  • AddThis Social Bookmark Button

Browse more Questions and Answers on AS/400 and Networking.

Looking for relevant AS/400 Whitepapers? Visit the Search400.com Research Library.


RSS - Discussions Help

Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

Graybeard52  |   Jun 9 2008  2:27PM GMT

CLient Access (aka iSeries Access) does indeed use port 23, in addition to port 8470, 8476, others. While it may be more work than its worth, iSeries Access can be configured to use a port other than 23. But I expect you would also have to update all the clients alos.

 

AnchorS  |   Jun 9 2008  7:34PM GMT

You won’t like this…….but how about you turning off auto config? Using telnet at the pc creates qpadevxxxx device assuming you have auto create turned on.

You’ll need to hit the clients to use a predefined/preconfigured workstation name, or you can have CA use the windows name, or device name. There is also an option in CA to add a suffix value at the end of the name if you are using the user name or device name to allow multiple signons.

My preference would be username plus a suffix to allow multiple Ca sessions.