Papercut popup not appearing

[DaveA]

Hi all,

 

After some much need help.

 

Yesterday on A-Level download day and our print server needed a restart. Took 2 hours to restart and when it came back online everything looked ok. I logged onto a few clients and the papercut balance windows comes up and says it is connected to the server but if you send a job to print nothing happens, you do not get the papercut popup appearing with either select and account of for staff or a message saying it is held in a queue for pupils and no jobs are getting to the print server.

 

Strangely some PC's that have not been restarted in a few days still seem to be working. You are able to use ID cards to access the copiers but they have no jobs to be printed.

 

Has anyone seen this before or have any advice for me to try?

 

Thanks

Dave.

[zedster]

Afternoon.

 

Without knowing server version or anything, i had a similar issue recently and it was due to a windows update. Take a look at what was installed recently, maybe remove them and reboot and see if that fixes the issue.

[DaveA]

Thanks Zedster you where spot on.

 

Any PC on 21H2 printed fine anything on 21H1 would not print. My job this week is to find any clients still on the older version

[ITGURU]

We've had this issue sporadically ever since getting Papercut. If users log off and back on, they then get the tray icon and popup to select account. Never got to the bottom of it, as we use the papercut client cached version.

[titch]

Thanks Zedster you where spot on.

 

Any PC on 21H2 printed fine anything on 21H1 would not print. My job this week is to find any clients still on the older version

We had the same after the print server updated. Had to reimage nearly the whole site in a couple of days to get printing going again. So many red herrings before figuring out it was the windows client version .

[ITGURU]

Can someone elaborate on this a bit more?

We're running Windows 10 21H1 and latest version of Papercut and seen no issues

[alanmorris]

Hi,

 

Do you know if the update had any impact on the new protocol requirement from Microsoft for Windows to Windows printing? The behavior in some cases is that the Windows clients can no longer copy the spool file to the print server.

 

I guess the question is, had you disabled the protocol prior to the update?

 

It's registry setting so you would if someone added the key for the protocol in order to disable it.

 

In January of 2021, Microsoft added a security protocol requirement in order to connect to shared printers. This protocol was disabled by default and if one wanted to enabled the protocol, you followed Microsoft guidance here: https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-changes-for-cve-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25

 

Microsoft turned on this protocol in September 2021 with unintended behavior by some version of Windows. The intention of the protocol is to block non Windows connections to shared printers and create a more secure connection when the client system is Windows.

 

Take a look for this registry setting on your print server. If it is not there, then you may wish to add the setting with a value of 0. This reverts the protocol to the behavior prior to September 2021.

 

At PaperCut, we have lots of people with Macs connecting to Windows and suggest the setting. We list the solution on a couple links to Known Issues. https://www.papercut.com/support/known-issues/#mf

 

 

1. Add a new registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\RpcAuthnLevelPrivacyEnabled (type DWORD)
   
2. Set the new key value to 0.
   
3. Restart the Print Spooler service.
   

This should allow Windows clients and macOS clients to print to the Windows Print Server, as before.

 

 

If by chance, the application on the client system hangs when submitting the job, the file is also not copied to the print server, I worked on an issue and Microsoft suggested disabling the protocol on the client systems which got them printing again.

 

 

Thanks