Thanks Chris.

I agree with you on the security. Some time ago it was decided that this was the way to configure things.


Paul Therrien
Orion South, Inc.
504-374-9551
800-437-7173
ptherrien@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Wednesday, May 16, 2012 4:35 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: RVI Client with invalid password disables common user - how can we find the culprit?

First fix your security. Everyone should have their own profile. You have no accountability for your RVI clients. That will never pass an audit. As for finding out who, well it was you generic RVI user who locked out the account. From where, well that is difficult to determine if you are not logging the IP address within the RVI server.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Therrien
Sent: Wednesday, May 16, 2012 2:01 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RVI Client with invalid password disables common user - how can we find the culprit?

We use RVI (Real Vision) for our imaging package to image IBM I spool files and other documents.
We have a single client profile that all users use to view images. Each RVI client connects with the same user profile and password.
One of our client machines seems to have a bad password as the user profile was disabled yesterday afternoon.
This did not affect anyone until this morning when people began signing in again with their RVI Clients.

I can see in the QHST log that the user profile was disabled, but I cannot see what job or connection caused the failure.
Is there a way I can find this information out? I guess I want the IP address of the PC that initiated the connection that caused the user profile to get disabled.

We have security auditing '*SECURITY' on, but this doesn't seem to give us what we want.


Paul

--
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.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].