Nmap Development mailing list archives

Re: Help with the results of a Scan, a bug?


From: David Fifield <david () bamsoftware com>
Date: Fri, 25 Jan 2013 10:05:43 -0800

On Fri, Jan 25, 2013 at 08:36:48AM +0000, Cuesta Quintanilla Alberto wrote:
Hi, here are the results of the following scan:

nmap -sT -sU -p 389,3268,3269,53,636,80,143,135,137,138,139,88,123,3389,445,25,5722,464,9389 -T4 -A -v x.x.x.x
PORT     STATE         SERVICE          VERSION
25/tcp   filtered      smtp
53/tcp   open          domain?
80/tcp   filtered      http
88/tcp   filtered      kerberos-sec
123/tcp  filtered      ntp
135/tcp  open          msrpc            Microsoft Windows RPC
137/tcp  filtered      netbios-ns
138/tcp  filtered      netbios-dgm
139/tcp  open          netbios-ssn
143/tcp  filtered      imap
389/tcp  filtered      ldap
445/tcp  filtered      microsoft-ds
464/tcp  filtered      kpasswd5
636/tcp  filtered      ldapssl
3268/tcp filtered      globalcatLDAP
3269/tcp filtered      globalcatLDAPssl
3389/tcp filtered      ms-wbt-server
5722/tcp filtered      msdfsr
9389/tcp filtered      unknown

However  if I do a telnet Destination_Server 445 or 389 for example, it works. Can you help me please?

Are the scan results the same every time? Please try these commands and
see if the output differs.

nmap -sT -p 389,445 x.x.x.x
nmap -sT -p 389,3268,3269,53,636,80,143,135,137,138,139,88,123,3389,445,25,5722,464,9389 -T3 x.x.x.x
nmap -sS -p 389,3268,3269,53,636,80,143,135,137,138,139,88,123,3389,445,25,5722,464,9389 -T4 x.x.x.x

David Fifield
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


Current thread: