Secure print jobs not being released to printer

When users try to release a secure print job at a Secure Release Here enabled printer, the job is not printed and remains visible on the terminal’s display. No error message is shown on the terminal’s display. Jobs submitted via a non-secure (direct) queue are printed successfully.

The most common cause is that the printer’s hostname connection in Blueprint can’t be resolved to the printer’s IP address. To confirm this is the cause:

1. Obtain the printer’s IP address. (Check the port configuration on the Windows print queue.)

2. On the Analyst, Open Blueprint Administrator -> Device Management -> Devices, and select the device record corresponding to the printer.

3. Go to the Connections tab and record the device’s hostname.

4. Check that Collector can resolve hostname to IP. Steps:

   • Open a command window on the Collector that hosts the secure queue.

   • Type “ping ”, excluding quotes, where is from step 3 above.

   • If ping returns that host could not be found, or an IP Address that does NOT match that given in step 1 above, then this is the cause of the problem.

Resolution:
 If the ping returns ‘host not found’, it means that there is no entry matching that hostname in the DNS system. The recommended solution is to add the required entry to DNS. An incorrect IP address usually means that the entry for the hostname in DNS (or the hosts file on the Collector) is incorrect. The recommended solution is to correct the entry in DNS or the hosts file.

Note: entries in the hosts file override DNS, so it’s possible that the entry in DNS is correct and the entry in the hosts file is incorrect.