In any network, you should know if someone is trying to gain unauthorized access. Novell provides a rather extensively configurable tool, "Intruder Lockout", which will lock down the account, but ConsoleOne only gives the last IP address of the attempted access. In most cases it's the legitimate user who calls you to say, "When I try to log in it says something like someone has tried to hack my account and it's locked up - who was it?". Therefore, the last IP from ConsoleOne may not be very useful for investigative purposes.
I found a simple and easy way to investigate "Intruder Lockout" history.
- Activate the reporting of "Failed Login Per Hour" in Health Monitor using Remote Manager (https://<yourserver>:8009) on each server to which users authenticate.
This lists each and every recent failed login attempt giving user account name, IP address, date and time.
- If you want, you can even set it to e-mail the triggered monitor report upon a certain threshold (default of 4 attempts) to you and if you have "Notify" activated in GroupWise you will be notified as it happens.
- Use the DNS\DHCP utility to find the computer name, which you can name by location from the IP address.
You therefore have a direct trace to the computer where the failed attempt(s) occurred, and if investigated quickly enough, the issue can often be solved as it happens. If a student is indeed playing around with accounts unauthorized and is confronted, I find news spreads quickly, and the instances diminish if not disappear altogether quickly - at least for a while ...
Short version of a very quick and easy setup:
- Enable "Intruder Lock Out" at a user account container level using ConsoleOne.
- Activate Server Health Monitor in Remote Manager to record and notify you of "Failed Logins Per Hour."
- Set up the mail notification when triggered.
- View the history from the notify or read it in Remote Manager and trace the source from the IP using DNS\DHCP Console if using DHCP.
- Netware 6.5
- Remote Manager
- ConsoleOne 1.3.6
- DNS/DHCP Management Console (if using DHCP)
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.