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 Pen-Test
[Top] [All Lists]

Identifying Windows O/S & SP

Subject: Identifying Windows O/S & SP
Date: Wed, 24 Aug 2005 18:52:30 -0400 (GMT-04:00)
    I am looking for a method of correctly identifying Windows O/S Versions and 
Service Packs remotely. Here are my restrictions:
- Performed Remotely (not in same broadcast domain)
- No Admin Rights on Remote Box
- No Username/Password on Remote Box
- VERY Few Packets Generated (excluding TCP 3-way handshake)
- Ability to **AVOID** IDS Detection

    My preferences are for something that is command line based, and can be run 
from a Linux platform. I'll take something GUI based or Windows based if that 
is all there is. Multiple tools are fine, as long as the number of packets 
generated are very low.

    I've taken a look at Winfingerprint 0.6.2 with only the Win32 OS Version 
option selected, but it generates 70+ packets which is too loud for my purposes.

<Prev in Thread] Current Thread [Next in Thread>