Intermapper vs Nmap

• The best thing about Intermapper is that it is map-based. You start by building your map, which is done completely automatically. I've used many different monitoring software packages, Solarwinds, Nagios, Opmanager, and it is a royal PITA to create live maps with those.
• Another great feature is that it shows you, visually, the bandwidth utilization of your network by using "ants" and color codes. Incredibly useful.
• Alarms are very easy to setup, again much easier than the packages mentioned above.

Read full review

• Nmap has a unique process of fingerprinting applications/devices to help us identify their communications patterns quicker.
• Nmap can be used for network auditing by specifying whole subnets that you would like to scan for open/closed ports.
• Nmap has a diverse presence and can be used from most operating systems.

Read full review

• Setting up probes in bulk can be difficult, so it can take a long time to get the system set up correctly to start.
• Sometimes the probes can be sensitive and report false positives.
• Interface can be a little clunky and non intuitive at times.

Read full review

• Maybe take some of the features of Zenmap and bake them in?
• Include fancy extra graphical results charts or graphs or something to show people who you want to convey info too but have no idea what Nmap is actually doing.
• I don't really think I'd change a lot actually.

Read full review

• Ability to provide real time alerting has proven to save our necks multiple times, since polling intervals could be set at a very low intervals.
• Real time monitoring of links provided ability to identify bottlenecks in real time!
• Writing custom probes, saved us thousands.

Read full review

• Positive return as it's open-source (free) on all OS's.
• If a person is not used of the command line there are a ton of front ends that make it point-and-click so the learning curve is good. That cuts down on time and manpower.

Read full review