Re: namp might report wrong port state

[David Fifield <david () bamsoftware com>]

On Tue, Sep 13, 2011 at 09:54:55PM +0800, Steve Zhou wrote:
> Hi nmap team,
>
>  
>
> Sorry for bothering, I have a question when I using nmap. I have an
> application listening on TCP pot 13456 runs on a server as you can see
> below. The name is ktconsService.exe.
>
> When I nmap to scan the port, it says the port state is "closed", but I can
> connect to the application without any issue.
>
> May I know why nmap reports the port state as "closed" even when the port
> can be connected?

Try running with the --reason option to see why the port is being marked
closed. You may also find more information with --packet-trace.

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