Sharing printer from Windows 11 (23H2) to previous Windows OS

[linkprogrami]

I recon question like this is not primarily for forum like this, but IQ of reditors is... questionable to be kind.

There seems to be an issue in sharing printers from Windows 11 (23H2) to previous versions of Windows. If I try to access the properly shared printer on Windows 11 from Windows 7 OS, double clicking on the printer gives 0x00000709 error, and trying to connect ot a printer gives "Cant connect to the printer" error.

Now based on previous expiriance, I am fairly sure its either some policy that Microsoft introduced or some registry setting that is making this problem. File sharing works perfectly even with WinXP OS.


SO anyone by any chance had this expiriance and knows the fix?

 

[linkprogrami]

Some additional info I experimented with:

Printer shared on Windows 11 (23H2) can be connected from Windows 11 (23H2)
Printer shared on Windows 11 (23H2) can be connected from Windows 10 (22H2, latest update Feb. 2024)
Printer shared on Windows 11 (23H2) canot be connected from Windows 10 (ver 2004)
Printer shared on Windows 11 (23H2) canot be connected from Windows 7 (SP1, latest updates, x64)

It is not the driver issue. It could be SMB issue, but file sharing works perfectly (even with WinXP). I tried various suggestions in terms of changing RPC policies and registry values, with no braketrhough so far.

Lastly, LPR/LPD sharing works perfectly and can be used to share the printer. Still would like to know if sharing can be done "natively", without having to resort to LPR/LPD.

 

[garlin]

The solution to Error 0x00000709 has been reported online for a while.

For network security reasons, 22H2 disabled RPC over Named Pipes as the default method for printer sharing. MS would prefer you to reconfigure all your remote clients to use RPC over TCP, but that's not always possible.

On the print host, integrate this reg fix:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC]
"RpcUseNamedPipeProtocol"=dword:00000001
"RpcProtocols"=dword:00000007
"ForceKerberosForRpc"=dword:00000001

 

[linkprogrami]

Hey again Garlin

So I applied the key, and what it did is: Now I do not get 0x00000709 when I double click, but I get the 0x00000011b when I try to double click or connect.

I think I did try this fix before with similar result.

 

[linkprogrami]

I FU**ING FIXED IT.

So its a two parts problem. First one was fixed by your regkey, 2nd part is adding RpcAuthnLevelPrivacyEnabled set as 0 in the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print"

Thank you so much Garlin for the assistance,

For everyone else dealing with this Microsoft change, please use the regkey below (apply key then reboot the PC):

 

[Gaurav]

i got a new error
scrn shot attached.

 

[garlin]

Is this a network printer, or local printer? If it's local, then check your printer drivers. Anyway if this isn't a network printer, please ask the same question on a new thread.