Anonymous_User Absent Member.
Absent Member.
923 views

Stupid IDL Tricks

Dear Abend,

At least once or twice a week we'll get a PC that is constantly IDLing
across the server console screen. It is usually caused by someone who has
a keyboard cover, a book or whatever laying on the keyboard Enter key
while the screen is in locked status. I've have also seen it caused by a
bad keyboard with a sticking key. There appears to be no way to stop the
constant IDL messages without physically finding the PC and fixing the
problem or turning it off. With 4500+ users in a 6 story building this
can be a royal pain...especially if the user is away from their desk and
can't be reached by phone.

Is there any other way? Is there an option at the client (4.91/SP2/NMAS)
or server end (NW65/SP5) to prevent constant IDL messages filling up the
CONLOG because some retard has a copy of The DaVinci Code sitting on their
keyboard? Why does NetWare keep reporting IDLs even AFTER the account has
been locked? I would think once it's locked the IDL messages should quit.

Sincerely,
Annoyed in DC
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Stupid IDL Tricks

chuck_perilli_nospam@navyfederal.org wrote:

> At least once or twice a week we'll get a PC that is constantly IDLing
> across the server console screen. It is usually caused by someone who has
> a keyboard cover, a book or whatever laying on the keyboard Enter key
> while the screen is in locked status. I've have also seen it caused by a
> bad keyboard with a sticking key. There appears to be no way to stop the
> constant IDL messages without physically finding the PC and fixing the
> problem or turning it off. With 4500+ users in a 6 story building this
> can be a royal pain...especially if the user is away from their desk and
> can't be reached by phone.
>
> Is there any other way? Is there an option at the client (4.91/SP2/NMAS)
> or server end (NW65/SP5) to prevent constant IDL messages filling up the
> CONLOG because some retard has a copy of The DaVinci Code sitting on their
> keyboard? Why does NetWare keep reporting IDLs even AFTER the account has
> been locked? I would think once it's locked the IDL messages should quit.


May want to also post in the server OS newsgroup / contact Novell OS
support, since its not up to the client workstation whether a
particular login attempt is going to be considered "an intruder".
(That's an eDirectory-side configuration, enforced and determined at
the server.)

A client-side defense that comes to mind is to find a key sequence its
harder to lay a book on. 😉 i.e. Enable the "Press CTRL-ALT-DEL to
logon" Windows policy (DisableCAD=0) such that someone would have to
pretty intentionally press CTRL-ALT-DEL to even begin a logon
sequence.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Stupid IDL Tricks

I'll try the Ctl-Alt-Del idea. I may also try posting on the OS board.
Thanks,

-Chuck


> chuck_perilli_nospam@navyfederal.org wrote:
>
> > At least once or twice a week we'll get a PC that is constantly IDLing
> > across the server console screen. It is usually caused by someone who

has
> > a keyboard cover, a book or whatever laying on the keyboard Enter key
> > while the screen is in locked status. I've have also seen it caused

by a
> > bad keyboard with a sticking key. There appears to be no way to stop

the
> > constant IDL messages without physically finding the PC and fixing the
> > problem or turning it off. With 4500+ users in a 6 story building

this
> > can be a royal pain...especially if the user is away from their desk

and
> > can't be reached by phone.
> >
> > Is there any other way? Is there an option at the client

(4.91/SP2/NMAS)
> > or server end (NW65/SP5) to prevent constant IDL messages filling up

the
> > CONLOG because some retard has a copy of The DaVinci Code sitting on

their
> > keyboard? Why does NetWare keep reporting IDLs even AFTER the account

has
> > been locked? I would think once it's locked the IDL messages should

quit.
>
> May want to also post in the server OS newsgroup / contact Novell OS
> support, since its not up to the client workstation whether a
> particular login attempt is going to be considered "an intruder".
> (That's an eDirectory-side configuration, enforced and determined at
> the server.)
>
> A client-side defense that comes to mind is to find a key sequence its
> harder to lay a book on. 😉 i.e. Enable the "Press CTRL-ALT-DEL to
> logon" Windows policy (DisableCAD=0) such that someone would have to
> pretty intentionally press CTRL-ALT-DEL to even begin a logon
> sequence.
>
> Alan Adams
> alancrumbadams@drcrumb.com
> (for email, remove the crumbs)


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.