MID Server (mid host name) is not a suitable MID because it does not have the following capabilities [{Capability: Nmap, value: null}]

[Hanumant Madan1]

Hi All,

We have been observing the log warning: 

MID Server (mid host name) is not a suitable MID because it does not have the following capabilities [{Capability: Nmap, value: null}]

We also found out that "mid.discovery.credentialless.enable" = True in our instance, and this is casuing that above message, and apparently, none of the MID servers seem to have NMAP installed, if they would have NMAP installed, I beleieve we should not have got that warning message.

I just need to confirm if NMAP is present or not on MID server, I see below is the way to check on windows:

on command prompt:  nmap- <version>

if NMAP is not installed, that means the property was set to True by default during upgrade from previous version to Paris version---just a guess, as this warning was not coming before.

And also, how do we find out if we have any devices discovered with "credentials less " discovery, as we are planning to disable this option considering the warning log.

Has anyone faced this and what was your take on it.

Regards,

HM

[Chuck Sellers1]

I did enable credentialess discovery for testing only on a developer instance and a local PC running the MID server. It said it would load NMAP on that server but when I kicked off a credentialess discovery I got the same error message and looked on the MID Server folder and there is no NMAP folder or nmap.exe in \agent\nmap. 

UPDATE: I kicked off the credentialess install of NMAP again and it did create the folder structure and put the requisite files in there but install still failed. Looked again and it removed all the files and the NMAP folder too. Kicked it off again and get the same result. It does start the process and then fails and removes the folder and files for NMAP.

FINAL UPDATE: I tried disabling anti-virus, firewall, rebooting MID server, etc. What finally fixed the issue was adding Windows Admin privileges to the local MID Server user account for the service on the Windows server. NOT GOOD, but since this is a PDI and a crash/burn virtual server I was able to run the NMAP install and kick off a successful credential-less scan.

Anyone know why had to elevate mid user to local admin privvy?

[Angelo Cortesi]

How It was easily solved.

1st attempt. (failed)

- Reinstalled MidServer with same same/different SN user properly granted

2n attempt. (success)

-Stopped the MidServer services

-Uninstalled Mid Server

-Reinstalled Mid Server with a new MidServer name, also using the same SN User used during the 1st Midserver installation

Root Cause: Uknown: Accepting yours insights based on it,