Re: scan IPs by port 5018 fail

[Daniel Miller <bonsaiviking () gmail com>]

Jim,

What is the output of your second command? You've got the --open option in
the first one, so I wonder if port 5018 is actually closed or filtered on
192.168.1.26. Nmap will still show it in the output, but the STATE column
will show something other than "open"

Dan

On Thu, Mar 17, 2016 at 10:31 PM, Jim White <nase0101 () gmail com> wrote:

> Hi nmap's dev
>     I ues nmap command like this
>         nmap -n -p 5018 -- open 192.168.1.1-30
>     Most of the hosts were discovered, but 192.168.1.26 was not much
> often. And I Command:
>         nmap -n -p 5018 192.168.1.26
>     Its port opened on 5018 indeed!!
>
>     Is there any suggestion? This problem happened in another environment
>
>     Thank you
>
>     --Jim
>
> _______________________________________________
> Sent through the dev mailing list
> https://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/