Most of it is encrypted and are only supposedly readable with an in-house program Xerox controls.
You won't find anything on your server anyway, the file is most certainly either a virus/trojan (it prints the file instead of executes it) or a file that was submitted via FTP mistakenly. In a lot of cases I have come across, a person actually sets up FTP scanning on the device, but they send the scan to the IP of the printer, which in effect is just a real weird way to do a copy ;-) . When the machine receives a file that appears print ready by FTP, it assumes it is a firmware update, when it turns out it is not, it prints it. Sadly, since the file is not proper, it prints the broken PS/PCL code.
You can disable Software updates by default and only turn them on when you are initiating an update to stop the ftp issue, and , if you use a print server, just disable RAW/port 9100 from printing (LPD is vastly superior, so use that), then any job would need to be IPP or LPD and both of which will show the submitter information if it is indeed something that was intended to print.
But, you can if need be go through Xerox (2nd level support) who can get your log file and send it to Engineering to decrypt and diagnose (Assuming you have a maintenance agreement this is not a billed service) I can state for a fact as a 2nd level rep, we cannot decrypt it, so as anything that goes to Engineering, it will be a long ways off of 1 day turnaround if you go that route.
Please be sure to select "
Accept Solution" and or select the thumbs up icon to enter
Kudos for posts that resolve your issues. Your feedback counts!
Joe Arseneau
