Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

DHCP Logging Locations

Subject: DHCP Logging Locations
Date: Tue, 30 Aug 2005 21:12:06 +0200
Background: Windows 2003 server environment, dynamic IP addressing (DHCP w/
logging disabled), 2003 DCs (full logging enabled), XP and W2K workstations
(full logging enabled), every machine is publicly accessible (not NATed).

Problem: I have old (nearly 1 month) information suggesting these several
workstations have been compromised. I only have the IP information for the
workstations at the time of the hack. Several of the workstations have
renewed their lease and others are mobile systems. With a network of
thousands of machines, is there a simple way to correlate the existing IP
address to the hostname? I'm thinking the DCs may contain the information if
the workstation had to authenticate to the DC. Are there any other areas I
can check? Thanks.

-Joel
 
 
---
"Illegitimis non carborundum."
Latin translation: "Don't let the bastards grind you down."

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 8/29/2005
 

<Prev in Thread] Current Thread [Next in Thread>
  • DHCP Logging Locations, Joel A. Folkerts <=