Solved Error 0x00000709 when connecting to shared printer Windows 11 22H2

spapakons · Dec 6, 2022

Hello! We recently upgraded our work computer from Windows 10 to Windows 11 64-bit 22H2 and also did a clean installation of Windows 11 22H2 at another computer. Neither of the two could connect to our shared printer with error 0x00000709. After a little Google search I discovered that this had to do because in version 22H2 the security default settings where changed. To be able to connect to the shared printer I had to change the security settings back to 21H2 default. More details at this link: Fix: Printer Error 0x00000bc4 or 0x00000709 in Windows 11 22H2 I did the Registry method, restarted and then I connected without any issue.

johnlgalt · Dec 6, 2022

Nice find! I'm surprised that they changed this, because in reading the GP notes for this value:

This policy setting controls which protocol and protocol settings to use for outgoing RPC connections to a remote print spooler.

By default, RPC over TCP is used and authentication is always enabled. For RPC over named pipes, authentication is always enabled for domain joined machines but disabled for non domain joined machines.

Protocol to use for outgoing RPC connections:
-- "RPC over TCP": Use RPC over TCP for outgoing RPC connections to a remote print spooler
-- "RPC over named pipes": Use RPC over named pipes for outgoing RPC connections to a remote print spooler

Use authentication for outgoing RPC over named pipes connections:
-- "Default": By default domain joined computers enable RPC authentication for RPC over named pipes while non domain joined computers disable RPC authentication for RPC over named pipes
-- "Authentication enabled": RPC authentication will be used for outgoing RPC over named pipes connections
-- "Authentication disabled": RPC authentication will not be used for outgoing RPC over named pipes connections

If you disable or do not configure this policy setting, the above defaults will be used.

Which indicated that this affects every single home and SMB computer running Windows 11 22H2 not joijed to a domain.

Why on earth would they do this?

spapakons · Dec 6, 2022

We don't have a domain at work. There are only five computers connected at a workgroup for simplicity sake. Only us use our computers and we all have Administrator rights. No restricted users involved, so to create a domain would be overkill.

spapakons · Jan 25, 2023

Thanks, I have already solved that. I recently upgraded one computer from Windows 10 to 11 and it had a problem connecting again because probably the fix was removed during the upgrade. I did the Registry fix again and could connect without any issue.

CCharles · Feb 14, 2023

I have a Windows 7 computer that is unable to install printers on two Windows 11 computers in a P2P network either using the adding printer or trying to connect to the printers using Windows Explorer. I have tried to do this with no success.
I'm able to install printers from another computer that has Windows 10. I'm also able to do a "net use lpt3" to the printer although it does not work if I assign it to the printer.
Any thoughts of what can I do more?
Thanks.

spapakons · Mar 11, 2023

Make sure the Windows 7 computer has the network connection set to "Work" or "Home", not "Public". Then that you have enabled File and Printer Sharing in Advanced Sharing Options. Then try to disable the password requirement. At Devices and Printers, right-click on the printer and Select Printer Properties. Verify that sharing is enabled and then go the the Security tab. Add the "Everyone" and allow it full access to the printer. This will allow any computer to connect as Guest to the printer. See if you can connect to the printer and print from another computer.

ITS · Sep 14, 2023

Now aday windows 11 really flipping idiot, try alot the method install LQ-310 (USB port) but the issues still same when perform sharing, even windows 11pro to windows 11pro also cannot be shared flipping FOOL OS.

spapakons · Sep 14, 2023

You must change the security method (not remember the exact term) using the Registry hack, see my original post. Do it on the host computer and if you still cannot connect do it on the guest computers too.