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
Software/Hardware used:
ASKED:
June 6, 2008 3:50 PM
UPDATED:
April 25, 2010 9:54 AM
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.
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.
Your question popped up when I Googled “telnet exit”.
Did you ever find an answer to your Client Access question?