Home page logo

basics logo Security Basics mailing list archives

Re: When nmap can't ID the OS...
From: xyberpix <xyberpix () xyberpix com>
Date: Sat, 04 Dec 2004 10:04:36 +0000

I know that there area couple of registry tweaks that can be added to
Windows(can't remember what they are at the moment), but that may be it.
I used to do it to all my boxes, Solaris, Windows, Linux, BSD, basically
just adding tweaks to change the TCP Seq ID.



On Fri, 2004-11-26 at 16:40 +0800, Derek Fountain wrote:
I have a remote server, which according to Netcraft, is running IIS-5.0 on 
Windows2000. I don't know for sure if that's the case, but it is believable.

When I used nmap (3.75) to ID the OS on it, it says it doesn't know. The 
machine has several ports open and none filtered, so I'd have thought nmap 
could work it out. I have a local machine running W2K and nmap can ID that 
(at least as far as telling me it's running some version on Windows).

What could be up with the remote machine that stops nmap IDing the OS it is 
For Security and Open Source news and tips visit:


Attachment: signature.asc
Description: This is a digitally signed message part

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]