New
#161
The KB5007253 update got me working again but not without some tweaks. I had to add the "RpcAuthnLevelPrivacyEnabled" = 0 described earlier in this thread. I added on both of my machines but it may work if you just add it on the host machine. I rebooted both machines and got the 0x0000016b printer install error which is farther than I was able to get before. Deleting the printer off of the machine that has the USB connection and then reinstalling the printer did the trick. You do have to go into the printer settings and share it again after the reinstall. After rebooting both machines I am finally able to print again. For now :)
- - - Updated - - -
- - - Updated - - -
Not needed. Thanks for offering.
The experiment has begun.
Last night I 'reset' all the PCs by deleting the RpcAuth registry key and any other edits I made, made sure all the spooler files are up to date (currently v1320), and did all updates on all PCs up to version 21H2 (but not KB5007253 yet).
All PCs should be "up to spec".
I can print from any PC to the network attached printers.
I can print from PCs with printers attached by USB to that attached printer.
I can't connect to, add, or print to the printer attached by USB to the server PC (Host) from any client PC.
As expected.
Next I plan to install KB5007253 on the server PC (Host) and test.
Then I will install it on the other PCs and test.
I'll let y'all know.
I installed the KB5007253 update on the print server (host PC with USB attached printer).
Remote PC (client) still can't install this printer.
Remote PC does not have KB5007253 installed. That will be next.
FYI: When I 'Add A Printer', and choose "Select a Shared Printer by Name", I can find the printer on the Host. It's when I click Next that the error message comes up "Can't Connect to the Printer".
For me it was only a client problem, since my network printer is not on windows, but on Linux using Samba, so dont know if the issue will be on a printserver running windows. My problem was i could not even install the printer on my windows. My printer stopped working, and i have been seaching everywhere, in the configuaration to find out windows update was the problem My computer could find the printer, but in the end could not print a test page, later i could not even add the printer anymore, but after the last update everything works smooth again :) But I think Microsoft used to long time to fix the problem! Some people said 3 months, I was a couple of updates behind, so I did not have the issue for more than 3 weeks or so .
- - - Updated - - -
That was excact the same problem I had, after the update everyting works again :)
So you are saying that after I install KB5007253 on the Client PC everything should work as expected.
I will see!
I'm doing things deliberately here so I can be sure where in the chain the problem gets solved.
Yes i will think it works after you installed the update at the Client, in my case the server was never the problem, cause it did not run windows, and Windows 7 printet fine on the same printer at the Linux server. Still my client pc windows 10 failed, but after the update, no problems to add the printer (before i got the message could not connect to printer), but after update, it works perfect :) hope if will work smooth for you too :)
I installed KB5007253 on one of the Client PCs this morning.
Can't add the remote printer that is on the Host (Print Server) PC. Same error message as before.
EDIT: I removed and reinstalled the USB printer on the Server.
Restarted both PCs.
No joy.
Last edited by TV2; 26 Nov 2021 at 11:05.
And...
Creating the Registry key RCPAuthnLevelPrivacyEnabled on the print server/host does not work as a workaround.
All fails end with error 0x0000011b.
The Registry hack used to solve the 11b error.
This post is incorrect. See Post #171
Last edited by TV2; 30 Nov 2021 at 08:38. Reason: Correction by OP
Installing RCPAuthn on both PCs does not work
Replacing the spooler file with v1237 does not work.
It would seem that this issue has been 'Resolved' in KB5007235 by killing "Point and Print" entirely.
I don't know if a printer already connected via P&P can be accessed using these past edits and hacks. I am past that.
This post is incorrect. See post #171
Last edited by TV2; 30 Nov 2021 at 08:39. Reason: Bad info