![]() This situation would happen with or without PaperCut. When this happens, the print job will never show up in the Windows print queue and will get cancelled without warning. We’ve seen cases where the print queue was added on a Windows WORKGROUP computer, and then later the user’s password expired or the account was disabled. Is the print job coming from a Windows workstation that’s not joined to the domain? If you’re seeing a ‘hold for authentication’ error in the print queue on the local macOS client, then take a look through the Troubleshooting ‘Hold for Authentication’ errors article. Is this a Mac client and are they seeing the notorious ‘hold for authentication’ error? If printing through the server is not desired, then one option is to install the PaperCut Direct Print Monitor on the user’s workstation so that these jobs can be tracked.Īt a minimum we need to make certain that the user is printing to a queue that is monitored by PaperCut, and that print jobs show up in the PaperCut Job Log, otherwise there is not much for PaperCut to track. You can ensure this by having the user connect to a shared print queue on the print server or by setting up PaperCut Mobility Print to share printers. If this is the case, consider deleting this print queue and connecting to the print server instead. It could be the case that the workstation is printing straight to a Bonjour-enabled printer, or directly to the IP address of the printer. If the print job isn’t reaching the server at all, then check to see how the printer connection is set up. The job never reaches the print server or printer… Is the print job somehow bypassing PaperCut? If this only happens with Mobility Print print jobs.If the job reaches the print server, the user can release the job, but nothing prints out….If the job reaches the print server and is held in the queue, but the user sees nothing to release….If the job reaches the print server but then disappears from the queue….If the job never reaches the print server or printer….Which behavior describes your issue the best? Does the job disappear immediately, does it stay held in the queue, or was it never there in the first place?.Then resume the job by unchecking ‘Pause Printing’.Does the Owner match the name of the PaperCut user?.Submit a print job that demonstrates the problem and ask these questions.Click on ‘Printer’ in the menu bar and check ‘Pause Printing’.Right-click on the printer and click ‘Open Printer Queue’.Open Print Management by pressing Windows key + R, then type printmanagement.msc and hit the enter key.To do this, try pausing the print queue on the server and attempt to recreate the issue: The first step is to narrow down where in the printing process the jobs are ‘disappearing’. Note: This next section is super important, and will set you up for ‘choosing your own adventure’ in the article, depending on what the behavior of your tests show! Troubleshooting jobs attributed to the wrong user or wrong owner name.Print Jobs aren’t being tracked by PaperCut.This will take you through in-depth troubleshooting for scenarios where you or your users are pressing print, but nothing is coming out of the printer, and there are no jobs showing up for release when you log into the printer or release station. This is a bit of a mammoth article, but hopefully it gets you immediate help in figuring out ‘where have my print jobs gone?’ “Help! Print jobs from our workstations don’t actually print.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |