I just started a trial of NTM and after scanning a few of my networks, I have a few questions:
1. What are the "unidentified_##" nodes suppose to represent in the scope of the application? At one of my sites, it accurately represents the fact that a Hyper-V host and VM are sharing the same physical interface for network connectivity. At another site, 4 UNID_## nodes create a tangled mess of connections that do not reflect reality at all (at least not physically).
2. My network does not have any routers. In the few scans I've done, three devices have been tagged by NTM as routers; a 2008 R2 server, an HP UPS, and an embedded Windows panel PC. The server might be explained by the routing/remote access feature being installed, but I have no explanation for the others.
3. The basic network hierarchy for my sites is firewall->switch->servers, and most of the endpoint devices respond to at least SNMP. At some sites NTM is able to connect nearly all of the devices correctly to the switch. At others, it cant make any of these connections. Are there any common things that might cause this type of behavior?
4. When rescanning a network, sometimes the scan says that previously discovered nodes like servers were not found. Is there any reason for this? These nodes have not been disconnected and are still pingable.
Thanks in advance for your help!
