|
I'm doing some work on an audit journal based failed signon type report...
I've got a good workable version, but am finding several instances
throughout the month where I get a large volume of entries with an invalid
user name bouncing off the system in rapid succession (causing maybe
1000 entries or so). I'm trying to figure out what is triggering
these... the devices are plant based terminals on our campus
(Powerterm 5250). I'll post a few examples below... they look more
like some type of glitch than any real login attempt. The examples
are an abbreviated listing from each of the instances... in reality
they take up 20-40 pages:
Type DATE TIME Job IPv4 Viol User
Device
Name IPv6
Typ Name
PW 2009/01/06 01:01:24 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:24 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:25 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:26 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:27 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:27 WINTER 4 U .
TPLT151
PW 2009/01/06 01:01:27 WINTER 4 U .
TPLT151
PW 2009/01/11 00:04:52 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:52 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:53 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:54 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:54 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:54 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/11 00:04:54 WINTER 4 U Q4141 0
TPLT101
PW 2009/01/22 11:03:08 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:09 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:10 WINTER 4 U .000000000
TPLT071
PW 2009/01/22 11:03:11 WINTER 4 U .000000000
TPLT071
--
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.
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.