I have installed BES scanner and Nmap 3.0. Tried scanning for the client but there were no results. I tried with Nmap 4.0, no results. I rebooted the system after installing Nmap. I followed all the guidlines on the site. There is no firewall or any program blocking the scan.
Hi Ben, I saw the site before. I am referring to NMAP scanner. I dont have any Fixlet for Asset discovery. I downloaded BES Scanner.zip, extracted it and executed. I tried with NMAP 3 and NMAP 4, but I was not able to get any results on my desktop.
The “BES Scanner” has been replaced a long time ago by the “BigFix Asset Discovery” Fixlet site that is much more powerful than the old standalone BES Scanner. We don’t support the BES Scanner anymore.
Quick question regarding the OS reference for Unamanaged assets. I’m wondering where the OS information is pulled from? Is it a best guess based on the MAC? Is this information pulled from the internet so it is most current or some embedded table in the underlying nmap software?
The OS is guessed at based on a sophsticated OS fingerprinting scheme that uses the network responses to differentiate OS types… Here is a lot more info on it for you:
we are currently updating our Asset Discovery content and as part of that project we will update the “Designate Nmap Scan Point” task to support installation on Windows 2008 Server.
When do you expect the new Asset Discovery tasks to be available? I am wanting to evaluate this functionality but the servers identified to host this function are Windows 2008.
Thanks,
Glynn Smith
annamin
Hi mcalvi,
we are currently updating our Asset Discovery content and as part of that project we will update the “Designate Nmap Scan Point” task to support installation on Windows 2008 Server.
Are there issues with simply changing the relevance to allow for installation on a windows 2008 server? I understand that it may not be a supported configuration, but it might help until there is a supported version that installs on win 2k8.
You can try it, but I believe something about Win2008 causes NMAP to not work the way we want it to so there is some work for us to support it… but I can check on that…