Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Re: tcp oddities.
From: Frank Knobbe (frankknobbe.us)
Date: Tue Sep 14 2004 - 22:36:58 CDT
On Tue, 2004-09-14 at 09:29, Josh Nunan wrote:
> After syn-scanning an IP block, I noticed that an ip
> address in the dns records as a mail server did not
> have tcp/25 open... I telnet'd to it... and to my
> suprise there was an smtp server sitting on port 25.
It looks like you have an IPS (or smart firewall) inline between
yourself and the mail server. The difference between the nmap SYN packet
and your TCP connect SYN packet is that the nmap SYN packet has a small
window size (1024) whereas your connect attempt sends a SYN packet with
a "normal" window size. Also, the SYN scan SYN packet does not include a
TCP option header that advertises the maximum segment size while the
connect SYN packet does.
So it would appear that you have an intelligent device that is able to
distinguish between an "nmap scan" (window=1024, no MSS) and a normal
connection attempt (window>1024, MSS present and >0).
Which means that for the rest of your engagement you might want to use
connect scans instead of just SYN scans :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
-----END PGP SIGNATURE-----