Error code 4005

Failure

When monitoring a network printer, the NDD Orbix portal displays a monitoring failure and does not capture information from the equipment.

The logs for the NDD - Printer Monitor service and NDD - Thermal Monitor service recorded error code 4005 (SnmpEntryException).

As a result, the printer may appear in search results but fail to complete registration, fail to send meter readings, or fail to display supplies.

Cause

The service was unable to access the printer’s IP address or load the SNMP entry.

The following log entry was recorded: [Error]An error occurred while trying to monitoration single printer. Reason: Failed to load snmp entry for <IP> Reason: Couldn't ping to ip: <IP> Error code: 4005

Related technical context:

• The printer may respond to other software but still be inaccessible to the NDD Orbix service.

• The SNMP community name may be incorrect.

• The IP address may be inaccessible from the service computer.

• The firmware may be out of date.

• There may be a network block between the computer and the printer.

• Verification must be performed from the computer where the service is installed.

Solution

1. Access the computer where the service is installed

2. Test communication with the printer’s IP address

3. Confirm that the IP address configured in the NDD Orbix portal is correct

4. Confirm that the printer is turned on

5. Confirm that the printer is connected to the network

6. Access the printer’s web interface and confirm that:

   1. SNMP is enabled;

   2. The SNMP community is set to public;

   3. Save the printer settings.

7. If necessary, restart the printer

8. Check if the printer’s firmware is up to date and update it if necessary

9. Perform a new printer discovery on the NDD Orbix portal

10. Verify that meter and supply data collection is now occurring normally

If the problem persists:

1. Enable service logs, as instructed at Configure and view service logs

2. Repeat the printer search process with the logs active

3. Collect the logs for analysis

Additional information:

• Ping or SNMP errors must be addressed in the network environment or in the printer configuration.

• Reading data via other software does not eliminate the need to validate SNMP, the route, and the computer’s permissions.

• Always test communication from the computer where the service is installed, not from other equipment.

• Outdated firmware may prevent capture, even with an accessible IP address.

• The SNMP community must be compatible with the configuration expected by the monitoring system.

• Blocking between VLANs, a local firewall, or network rules may prevent capture.

Last updated: July 07, 2026