Re: Strange iSeries Access Operations Console Behavior

[Al Mac <macwheel99@xxxxxxxxxxx>]

Depending on settings in your system values, if someone does too many 
consecutive wrong guesses of a password, that sign on gets disabled.  It 
might not be that a human being screwed up.  Sometimes a PC connection is 
flakey, and the AS/400 interprets a series of connect, disconnect as the 
same thing as try to sign on but forget password, and treats this as an 
intruder to be disabled.

If you have QSYSMSG setup, it gets copies of security related messages such 
as some password disabled for whatever reason.

Various passwords come from IBM "out of the box"
They should be changed to something known only to your staff, so that 
mischevous people not mess you up.
They should be changed again periodically, in case too many people now know 
them.
You have to have some way of remembering or figuring out what you changed 
them to in case you not often need to use them.
It helps to have a list of who is authorized to mess with this stuff, so 
that when you change the passwords, the right people get notified.

In the SST/DST area, upper and lower case is also critical with the passwords.

Al Macintyre
AS/400 computer data janitor

> OPS Console  uses at least "1" of the SST/DST user ID's to establish the
> initial connection. Most of the time this ID is '11111111' ( 8 #1s).  The
> default password for that ID is also '11111111' but it can be changed.
> Other default IDs available are '22222222' 'QSRV' and 'QSECOFR'. All of
> these ID's are stored separately from their OS versions. what may have
> happened is that 1 or more of these SST/DST IDs are disabled
> _____________________
> Kirk Goins CCNA
> Systems Engineer, Manage Inc.
> IBM Certified i5 Solution Sales
> IBM Certified iSeries Solutions Expert
> IBM Certified Designing IBM e-business Solutions
> Office 503-353-1721 x106 Cell 503-577-9519
> kirkg@xxxxxxxxxxxxx      www.manageinc.com
>
> There are 10 types of people in the world:
> Those that understand binary, and those that don't.
>
>
>
> Paul Tykodi <ptykodi@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 11/17/2005 03:00 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> midrange-l@xxxxxxxxxxxx
> cc
>
> Subject
> Strange iSeries Access Operations Console Behavior
>
>
>
>
>
>
>
> Dear List,
>
>   I am doing some work for a customer who has an iSeries 9406-800 running
> V5R2. They use a PC (Win XP sp2) as their iSeries console. It is connected
> to the iSeries server using a special cable provided by IBM and the cable
> connects to a board in the iSeries back plane. The setup appears to allow
> the iSeries Access Operations Console software to establish a high speed
> serial communication link with the iSeries server.
>
>   Recently the PC software has claimed that all of the iSeries server
> administrative user ID's are disabled and this has caused the console
> function to stop working due to logon failure. When I plugged a twinax
> terminal into the iSeries, I found that at the server end of the
> communication all of the user ID's are fine and the system is running
> fine.
>
>   It seems like the iSeries Access Operations Console software may have
> written some erroneous password information to the registry and that has
> caused it to fail. The un-install and re-install of the software does not
> resolve the problem.
>
>   The PC is at the latest iSeries Access service pack for V5R2.
>
>   Does anyone know what registry keys might have become corrupted to cause
> this unexpected behavior?
>
>   Thanks.
>
>   Best Regards,
>
>   /Paul
>   --
>   Paul Tykodi
>   Principal Consultant
>   TCS - Tykodi Consulting Services LLC
>
>   E-mail: ptykodi@xxxxxxxxxx
>
>
> ---------------------------------
>  Yahoo! FareChase - Search multiple travel sites in one click.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.

-
Al Macintyre  http://www.ryze.com/go/Al9Mac
BPCS/400 Computer Janitor ... see
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html