Re: NMAP : Different interpretation of "filtered" ports depending on -sS or -sT options. Bug ?

[Sébastien CONTRERAS <contrera () EIG UNIGE CH>]

According with previous responses, I think that NMAP version 3.75 for 
Windows (perhaps also previous versions) has a bug when doing a -sT scan 
(NMAP doesn't see the TCP Rst, Ack sent by the scanned machine).
Can somebody confirm this behaviour by testing the following command line on 
a Windows XP machine ? The machine with IP x.x.x.x musn't be protected by a 
firewall and must have the 135 port (or another port) open and the 136 port 
(or another port) closed
nmap.exe -sS -p 135-136 -P0 x.x.x.x
nmap.exe -sT -p 135-136 -P0 x.x.x.x

If the second command line tells you that port 136 is filtered, the version 
of NMAP is certainly bugged. If it's really a bug, can someone refer it to 
nmap developers ?


---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List archive: http://seclists.org