Total Network Inventory vs Competitors: Feature Comparison and Pricing

Troubleshooting Common Issues in Total Network Inventory Deployments

1. Discovery fails or misses devices

• Likely causes: incorrect credentials, firewall/port blocking, SNMP/WMI disabled, wrong IP range/subnet.
• Fixes: verify credentials (WMI/WinRM for Windows, SNMP community for network devices), open required ports (TCP 135, 445, WinRM ports; SNMP UDP 161), enable and configure SNMP/WMI/WinRM on targets, confirm correct scanning ranges and network segmentation, add device exceptions for VLANs or subnets.

2. Incomplete or incorrect hardware/software data

• Likely causes: outdated agents, limited permissions, unsupported device types, OS reporting restrictions.
• Fixes: install or update the inventory agent where available, grant read-level admin rights for WMI/WinRM, update device SNMP MIBs if needed, ensure latest TNI version to support new OS/hardware, use alternate discovery methods (agentless vs agent-based) to cross-check.

3. Slow inventory scans or high network load

• Likely causes: aggressive scan concurrency, large IP ranges scanned without filters, scanning during peak hours.
• Fixes: reduce concurrent threads, schedule scans during off-peak hours, narrow discovery ranges, exclude known offline IPs, enable bandwidth-friendly options in settings, use distributed scanning if supported.

4. Authentication errors

• Likely causes: expired/locked accounts, wrong domain formatting, policies blocking remote auth (UAC, restricted firewall).
• Fixes: verify account status and password, use DOMAIN\username or username@domain format as required, enable remote UAC exceptions or configure LocalAccountTokenFilterPolicy for local accounts, ensure target machines allow remote management.

5. Agent installation or update failures

• Likely causes: endpoint security blocking installers, group policy conflicts, network connectivity issues.
• Fixes: whitelist installer in AV/endpoint protection, deploy via GPO or remote management tool, check MSI/log output for errors, ensure ports and share access for installation files.

6. License or activation problems

• Likely causes: license limit exceeded, incorrect license file, time/date mismatches.
• Fixes: verify license capacity and assigned agents/devices, reapply license file or re-activate through vendor portal, ensure server/system time is correct.

7. Reporting discrepancies or export failures

• Likely causes: corrupted database, mismatched schema after upgrade, permissions on export paths.
• Fixes: run database integrity checks, follow upgrade migration steps from vendor, grant write permissions to export folders, export smaller datasets to isolate problem.

8. UI or server crashes

• Likely causes: insufficient resources, corrupted cache, incompatible plugins/extensions.
• Fixes: increase server RAM/CPU, clear application cache/logs, review logs for errors, disable third-party integrations and re-enable one-by-one, update to latest stable release.

9. Inability to scan cloud or remote networks

• Likely causes: missing VPN/connector, NAT/port translation, lack of credentials for cloud APIs.
• Fixes: deploy remote scanners/connectors in target network, configure VPN or site-to-site connectivity, use cloud API credentials where supported (AWS/Azure), open required ports and configure NAT traversal.

10. Unexpected device duplication

• Likely causes: multiple discovery methods picking same device, IP changes/DHCP churn, hostname resolution conflicts.
• Fixes: enable device deduplication settings, prefer stable identifiers (MAC, serial number, UUID) for matching, adjust discovery rules to avoid overlaps, synchronize with DHCP/CMDB to track dynamic IPs.

Quick troubleshooting checklist

1. Confirm network connectivity and required ports.
2. Verify credentials and permissions.
3. Check TNI version and update agents.
4. Review logs (server and agent) for errors.
5. Reduce concurrency and reschedule heavy scans.
6. Validate license and disk/database health.

If you want, I can produce step-by-step commands for checking WMI/WinRM/SNMP, or a diagnosis script tailored to Windows/Linux agents.