RADARPRINT GUIDE

Troubleshooting connectivity by layer

Test user-to-server, device-to-server and server-to-device paths separately.

In this guide

There is more than one connection

An administrator may be able to open the console while a device cannot open its panel. Different network segments, DNS or certificate trust may explain this. Describe which component cannot reach which destination.

Investigation order

  1. Check access to the correct server name from a user workstation.
  2. Verify that the device network can resolve and reach the same destination.
  3. Inspect server access to the required management and print services on the device.
  4. Test SNMP independently of web panel access.
  5. Review SMTP and Active Directory against their own destinations.

After a network change

Start with recent server IP, DNS, VLAN or firewall changes. Devices may retain an old address. Confirm required ports for the selected integration and deployment package.

Support record

Record source and destination components, timestamp, last successful operation and recent changes. Investigate the failing connection narrowly instead of disabling the entire firewall. Review held jobs and user impact before restarting production services.