Common reasons devices are not automatically discovered by a Print Tracker Pro data collection agent (DCA)/installation:
The installation's settings > device discovery > 'IP addresses to scan' list does not include the network segment of the device.
If the device network segment is known enter it, save the change.
To expedite discovery submit an on-demand scan as described at https://docs.printtrackerpro.com/docs/guides/discovery#on-demand-scans.
The entity's and installation's simple network management protocol (SNMP) settings differ from those used by the installation. Normally installation's inherit SNMP settings from the parent entity.
Devices normally have SNMP enabled, either version 1, 2c, or 3
Device community strings are often left blank or set to: public
The installation's SNMP timeout setting is to low.
Most devices will return SNMP version 1 or 2c data with a timeout of 1000ms
Some devices may be slow to respond, especially if using SNMP version 3, in which case a timeout of 3000 is recommended.
The device SNMP port is not set to port 161
The installation is without network access to the device (unable to PING or get back SNMP).
Common reasons are: the device is turned-off, device or network security is blocking communication.
Running a network topology scan from the installations > 'Network Topology' screen shown in the example below will indicate if the DCA can communicate with the device.
Once the scan completes results will indicate if each IP address:
returned a PING
returned SNMP over port 161
has a detected embedded web server
returned SNMP that confirms the device is a printer or copier
