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

linkprogrami

New Member
Messages
22
Reaction score
14
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?
 

Attachments

  • VirtualBox_Cavia Porcellus (W7-64)_13_03_2024_23_17_29.png
    VirtualBox_Cavia Porcellus (W7-64)_13_03_2024_23_17_29.png
    71.2 KB
  • VirtualBox_Cavia Porcellus (W7-64)_13_03_2024_23_17_59.png
    VirtualBox_Cavia Porcellus (W7-64)_13_03_2024_23_17_59.png
    71.7 KB
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.
 
The solution to Error 0x00000709 has been shared online for a while.

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

On the printer's host, add this reg file fix:
Code:
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
 
Hey again Garlin :D

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.
 

Attachments

  • VirtualBox_Cavia Porcellus (W7-64)_14_03_2024_16_45_41.png
    VirtualBox_Cavia Porcellus (W7-64)_14_03_2024_16_45_41.png
    126.5 KB
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
 

Attachments

Last edited:
i got a new error
scrn shot attached.
 

Attachments

  • Screenshot 2024-04-20 165057.png
    Screenshot 2024-04-20 165057.png
    19.1 KB
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.
 
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:
Code:
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
thanks. it works
 
I also found that this solved the issue of me not being able to install apps from my QNAP share (instead I would have to copy them to disk and than install).

It feels like Microsoft lifts a leg like they gonna do a step forward, but it was just a cartoonish prep to do a comedic tumbling backwards...
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
Hey man, thanks for the fix. Appreciate it
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
Thank you legend! This worked perfectly.
 
If you have a networked printer, like many HP models, then you can bypass printer sharing and directly communicate. You may need to setup some network routing, or use manual IP setup instead of network discovery. But most mid-range printers now have built-in Ethernet and WiFi.
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
Cảm ơn bạn rất nhiều. Tôi đã thử rất nhiều cách khác nhau liên quan đến registry nhưng đều không được. Sau khi thực hiện bước này của bạn máy tính window11 đã kết nối được đến máy in được chia sẻ kết nối với máy tinh window 10

Mod Note:
(provided English translation)
Thank you very much. I have tried many different ways related to the registry but none of them worked. After doing this step, your window11 computer was able to connect to the shared printer connected to the window 10 computer.
 
Last edited by a moderator:
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
FUNCIONA!! AGUANTE MESSI
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
Thank you so much for sharing
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
I searched for the solution for several weeks, I tried several methods, I reinstalled Windows many times, but the only solution that worked was the one you shared here, thanks! It can't be that the incompetent Microsoft engineers haven't fixed it before with an update
 
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):

Code:
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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
Thank you brooo...this work perfectly
 
The solution to Error 0x00000709 has been shared online for a while.

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

On the printer's host, add this reg file fix:
Code:
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
thank you very much...
 
Back
Top