HI,
We observed Discovery scan prints junk characters on several printers like Toshiba printers. We have done local troubleshooting and asking vendors to check but still couldn’t solve this issue.
Hi Naveen!
You are running into a common phenomenon with scanning printers where interacting with their HTTP services causes unwanted results such as printing junk pages. The most robust way of addressing those issues is to prevent the scans from interacting with the HTTP services of the printers. You can do that by using a scan template that doesn’t scan the ports associated with those services. Those would be commonly available through ports 80, 515, 9100-9107, 9220 and 9500.
If this doesn’t help, your best bet is to open a support case in the Customer Portal.
7 Likes
Try excluding ports 9100-9114,9400 in your Template under the “Service Discovery” tab in the scan template configuration.
3 Likes
Thank you for this thread - it resolved this for us without opening a ticket.
We just discovered this is the cause of a “gibberish print job” issue we have had for some time. We “connected the dots” today when doing discovery and first vul scans on new printers. Removing only port 9100 from “SERVICE DISCOVERY - Additional ports” from our scan templates was enough to resolve the problem. We also had to create a custom “Full Audit” template that excludes port 9100 TCP/UDP and then separate our scan jobs using a dynamic group tied to a scan site.
Craig