+3Our users that have recently upgraded to Big sur 11.6.3 or 11.6.4 have had printing issues to our Ricoh printers. Monterey 12.2.1 might also be affected.
We are having to re-install the printer drivers for each user. is anyone else experiencing this?
Tim
Best answer by jc0b
Are you printing to them using smb? Smb printing is currently broken in 11.6.3, 11.6.4, 12.2(.1) and macOS Catalina with the 2022-001 security update. This is due to a combination of updates to Windows Server to mitigate PrintNightmare, and updates to macOS to support a new addition to the authentication mechanism in Windows Server. Unfortunately, the implementation in macOS seems to be buggy.
There are some workarounds, but they don’t work for everyone. It sounds like the issue is fixed in 12.3, so hoping the fix will be backported to 11 and 10.15. In the meantime, if you can print via any other protocol than SMB (such as IPP), do that. Only the SMB protocol is affected.
+3Are you printing to them using smb? Smb printing is currently broken in 11.6.3, 11.6.4, 12.2(.1) and macOS Catalina with the 2022-001 security update. This is due to a combination of updates to Windows Server to mitigate PrintNightmare, and updates to macOS to support a new addition to the authentication mechanism in Windows Server. Unfortunately, the implementation in macOS seems to be buggy.
There are some workarounds, but they don’t work for everyone. It sounds like the issue is fixed in 12.3, so hoping the fix will be backported to 11 and 10.15. In the meantime, if you can print via any other protocol than SMB (such as IPP), do that. Only the SMB protocol is affected.
+14The Apple fixes for SMB printing were issued in 11.6.3 and 12.2.0 (supporting changes to the SMB protocol) and I was able to have printing working again after these updates were applied with the standard SMB print queues. My current issue however is that the queue configured by Jamf Pro is broken, but a manually configured queue is working. I've also done some digging into CUPS, the /etc/cups/printers.conf file and been working on a script that allows us to setup our queue via Self Service again.
+3Thank you both for your answers! Yes, we use SMB, and that is the issue. We are converting over to IPP as we speak.
Thanks again!
+7The workaround we've been using is to append ?encryption=no to the printer URI. Ie
smb://printserver.domain.com/PRINTER?encryption=no
If you set the printers through the built in function in Jamf Pro you can just edit the Device URI and re-deploy the printer. If you don't change the name it just overwrites the existing printer, a good thing in this case.
+1The workaround we've been using is to append ?encryption=no to the printer URI. Ie
smb://printserver.domain.com/PRINTER?encryption=no
If you set the printers through the built in function in Jamf Pro you can just edit the Device URI and re-deploy the printer. If you don't change the name it just overwrites the existing printer, a good thing in this case.
why lpd would not work, using ?encryption=no
any tricks for lpd to work where it does not prompt for authentication?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.