Nmap Development mailing list archives

Re: service misidentification


From: Daniel Miller <bonsaiviking () gmail com>
Date: Thu, 23 Jun 2016 19:23:41 -0500

Did you forget to install OpenSSL development headers? Try nmap --version
to see.

Dan
On Jun 23, 2016 3:00 PM, "Josh Amishav-Zlatin" <jamuse () gmail com> wrote:

When I run nmap v6.47 against an RDP server on a non-standard port, the
service is correctly identified. However, when I run the same command using
nmap 7.12SVN the service is not correctly identified. For example:

#:/opt/nmap-6.47# ./nmap -A -p 33896 -Pn x.x.x.x
...
PORT      STATE SERVICE       VERSION
33896/tcp open  ms-wbt-server Microsoft Terminal Service

#:/opt/nmap-7.12SVN# ./nmap -A -p 33896 -Pn x.x.x.x
...
PORT      STATE SERVICE       VERSION
33896/tcp open  ssl/unknown

I've tried setting the --version-intensity to 9, but no joy. How can I
debug and fix this issue?

_______________________________________________
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/

Current thread: