Windows 11 22H2: Network printers communitcate now via RPC over TCP by default

Windows[German]Note to administrators in corporate environments who manage Windows 11 clients and are upgrading to version 22H2. There is a change in the connection of network printers, the connections are now done with RPC over TCP, as Microsoft has disclosed in a post.


I was alerted to the release via the following tweet, This may be relevant to administrators who need to know what changes to the printing components were introduced with Windows 11, version 22H2.

It's changes the way Windows computers communicate with each other when printing or performing print-related operations on the network. For example, the changes take effect when communicating with a printer shared by a print server or another computer on the network. Microsoft writes that these changes were made to further improve the overall security of printing on Windows.

  • For print-related communications, RPC over TCP is used by default for client-server communications.
  • The use of RPC over Named Pipes for print-related communication between computers is still possible, but is disabled by default.
  • The use of RPC over TCP or RPC over Named Pipes for print-related communication can be controlled by Group Policy or through the registry.
    By default, the client or server only listens for incoming connections over RPC over TCP.
  • The Spooler service can be configured to also listen for incoming connections over RPC over Named Pipes. This is not the default configuration.

This behavior can be controlled by group policy or through the registry. When using RPC over TCP, a specific port can be configured for communication instead of using dynamic ports. Environments where all computers belong to a domain and support Kerberos can now enforce Kerberos authentication. The details can be found in the support article RPC connection updates for print in Windows 11.

Cookies helps to fund this blog: Cookie settings

This entry was posted in Windows and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *