Re: Trying to track a hacker
From: Karl Levinson [x y] mvp (levinson_k@excite.com)
Date: 11/19/02
- Next message: Karl Levinson [x y] mvp: "Re: Separating networks"
- Previous message: Karl Levinson [x y] mvp: "Re: NT File Security"
- In reply to: Dan Morris: "Trying to track a hacker"
- Next in thread: SvS: "Re: Trying to track a hacker"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Karl Levinson [x y] mvp" <levinson_k@excite.com> Date: Tue, 19 Nov 2002 13:54:40 -0500
"Dan Morris" <dmorris@aacb.com> wrote in message
news:98dd01c28fef$40d87b00$8af82ecf@TK2MSFTNGXA03...
> Recently someone has been trying to hack into our
> domain. In the event log we can see multiple failed
> attempts for multiple users, reulting in accounts being
> locked out. The name of the workstation it comes from
> constantly changes and is not a workstation that we are
> aware of on our network. Is there any way to reliably
> get the IP address of whoever is trying to log in. Such
> as something that would capture all failed log on
> attempts and the IP address they came from.
There is no native way in Windows to get the IP address. You need third
party sniffer or firewall software or hardware, even a free version such as
www.sygate.com, [firewall], www.ethereal.com, http://windump.polito.it, or
the Network Monitor feature that comes with Windows 2000 / XP / NT [under
start, settings, control panel, add remove programs, add remove windows
components]. You would need to install the software onto all domain
controllers or computer being logged into, especially if the login attempts
are from machines on the local network. I hesitate to recommend Sygate on a
domain controller since I had a difficult time uninstalling it on one DC
[had to boot to Directory Services Restore mode to uninstall and reinstall
the IP stack and edit the registry], but for workstations it is easy and one
of my favorites.
If these people are logging in from the internet, you need a firewall to
protect your network and stop your network from leaking passwords, login IDs
and other information to any anonymous user who wants them. There are free
firewalls out there, so there's no excuse not to. For a list of free and
not-free firewalls, see:
http://securityadmin.info/faq.htm#firewall
- Next message: Karl Levinson [x y] mvp: "Re: Separating networks"
- Previous message: Karl Levinson [x y] mvp: "Re: NT File Security"
- In reply to: Dan Morris: "Trying to track a hacker"
- Next in thread: SvS: "Re: Trying to track a hacker"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|