- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-28-2024 01:31 AM
We configured network mapper in the BrokerVM settings and using multiple ports for network identification. Of course, on the firewalls we allow all traffic from them to make a full visibility internally. However, the scan doesn't resolve the hostname or open ports on the machine that can support with OS identification, like 22/ssh - potential Linux etc. Sometimes with manual scan using nmap we can see much more open ports and zero return from mapper.
Using network mapper, possible to resolve FQDN of the machine like with nmap ARP scan? How possible to identify or which process is the best to identify unknown assets in the network?
12-27-2024 07:53 AM
Hi MDovirak,
The Broker VM Network Mapper is only using a ping scan to identify interfaces on the network. It is not doing nmap or any other method that would allow more detailed discovery. You can ingest DHCP logs from Microsoft DHCP to provide additional enrichment of hostname for discovered IP addresses.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!