Share via

Windows Server 2012 R2 printers not showing on Windows 11 22H2

Jan Schulenburg 106 Reputation points
2022-09-23T12:01:14.68+00:00

We're testing W11 22H2 within our environment and almost everything is working. Almost, one key part, printing, is causing an issue. When trying to connect to a Windows Server 2012R2 printserver it says it can't connect. On Windows 10, our current workstation OS, this works fine. Manually connecting to the printer (using the UNC path) also gives an error:

  • connecting: Windows couldn't connect to the printer. Check the printer name and try again. If this is a network printer make sure that the printer is turned on, and that the printer address is correct. In the Event Viewer the error is 1801
  • double click: Operation could not be completed (error 0x00000709). Double check the printer name and make sure that the printer is connected to the network

The new printserver is running Windows Server 2022 and printers on that server are connected just fine on Windows 11 and Windows 10.

Does anyone have the same and what can we do about this? It seems something on the Windows 2012 R2 not accepting the connect request from a W11 22H2 device?

Additional info: with Windows 11 21H2 printers will connect fine, after upgrading using the Windows 11 Installation Assistant to 22H2 it's broken so it seems a bug to me!

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,590 questions
Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
680 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
9,686 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jan Schulenburg 106 Reputation points
    2022-09-27T10:33:28.443+00:00

    The solution is to set a newly introduced printer policy:

    • Configure RPC connection settings: Enabled
    • Protocol to use for outgoing RPC connections: RPC over named pipes
    • Use authentication for outgoing RPC connections: Default

    After reboot the connection with the Windows Server 2012R2 and 2022 printers can be made!

    3 people found this answer helpful.
  2. Alan Morris 1,161 Reputation points
    2022-09-26T16:00:07.827+00:00

    1801, 0x709 in hex, is invalid printer name.

    Is the server name actually the server name? Your not using a CName record, correct?

    Can you connect to the IPv4 address from Win11? \1.2.3.4. Substitute the IP of the server. The spooler on the server will internally register the name and IP for connection responses.

    All the clients connect to the same domain, correct?

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.