ERROR 0X00000709 ON WIN 11 PRO 26H2

calvin teng 0 Reputation points
2026-10-07T05:16:40.1133333+00:00

all my client pc which win 10 and win 11 cant even get to shared the printer from the host which is win 11 pro.

which i know win 11 is having this big issue. what is the accurate solution for this?

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 1,900 Reputation points Microsoft External Staff Moderator
    2026-10-08T02:54:24.4566667+00:00

    Welcome to Microsoft Q&A!

    Thank you for the detailed information and for confirming that you have already tried the suggested troubleshooting steps.

    Since you have already checked the standard printer sharing settings, network discovery, credentials, and manually connected using \\ComputerName\PrinterShareName, the next step I would suggest is checking the RPC communication between an affected client and the Windows 11 host.

    On one of the affected client computers, open PowerShell and run:

    Test-NetConnection -ComputerName HOSTNAME -Port 135

    Replace HOSTNAME with the actual computer name of the Windows 11 PC that is sharing the printer.

    If TcpTestSucceeded returns False, this indicates that connectivity to TCP port 135 is not succeeding. In that situation, I would investigate the network and firewall configuration between the client and host before continuing to remove and reinstall the shared printer.

    Also, you can review the printer RPC policy settings:

    1. Run gpedit.msc.
    2. Go to Computer Configuration > Administrative Templates > Printers.
    3. Open Configure RPC connection settings.
    4. Check which RPC protocol is configured for outgoing printer connections.
    5. On the Windows 11 host, also review Configure RPC listener settings and check whether its incoming printer RPC configuration is compatible with the client configuration.
    6. If you make any changes, restart

    If port 135 is reachable but you continue to receive error 0x00000709, please check the following:

    • Does \\HOSTNAME open successfully from the affected client?
    • Are you connecting to the host using its actual computer name, an IP address, or a DNS alias?
    • Does error 0x00000709 occur while adding the shared printer, or only when you try to print?

    One additional point worth checking is the computer name being used to access the printer. If you are connecting through a DNS CNAME/alias, please try using the Windows 11 PC's actual computer name instead. Microsoft has documented a scenario in which error 0x00000709 can occur when accessing a print server through a CNAME.

    At this stage, I would avoid making multiple registry changes without first narrowing down the cause. The results of the checks above should help determine whether the issue is related to network/RPC connectivity, name resolution, or another part of the shared printer connection process.

    If the issue still occurs after completing these checks and the same behavior can be reproduced on a clean Windows installation without relevant policies or custom configurations applied, I would recommend submitting the issue through the Feedback Hub for further review.

    When submitting the feedback, select Problem and choose the category related to Devices and Drivers > Printing. It would also be helpful to include error 0x00000709, the Windows version and OS build, and clear steps for reproducing the issue. If necessary, you can also consider contacting Microsoft Support for more in-depth investigation.

    I hope these additional checks help narrow down the cause.

    References:

    Error 0x00000709 when you use CNAME record - Windows Client | Microsoft Learn

    Fix shared printer connection problems in Windows | Microsoft Support

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments
  2. calvin teng 0 Reputation points
    2026-10-07T05:35:27.49+00:00

    i have try all this method but still failed :(

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-10-07T05:16:56.35+00:00

    For a shared printer hosted on Windows 11 Pro, use this troubleshooting path first:

    1. On the host PC, confirm the printer is actually shared:
      • Start > Settings > Bluetooth & devices > Printers & scanners
      • Select the printer > Printer properties
      • Open the Sharing tab
      • Turn on Share this printer
      • Confirm the Share name
    2. Verify the client PCs can reach the host:
      • Make sure both PCs are on the same local network.
      • On a client PC, open File Explorer and enter \\ComputerName in the address bar.
      • If the host PC is not reachable, fix network or name-resolution issues first.
    3. Check sharing settings on the host and clients:
      • Start > Settings > Network & internet > Advanced network settings
      • Open Advanced sharing settings
      • Turn on Network discovery
      • Turn on File and printer sharing
      • Save changes
    4. Use correct credentials when connecting:
      • Use the same Microsoft account or local user account on both PCs, or
      • When prompted, enter the username and password of the host PC.
    5. Add the printer manually on each client instead of relying on automatic discovery:
      • Start > Settings > Bluetooth & devices > Printers & scanners
      • Select Add device
      • If the printer is not listed, select Add manually
      • Choose Select a shared printer by name
      • Enter the path as \\ComputerName\PrinterShareName
      • Complete the on-screen steps
    6. If it still fails, remove and reconnect the shared printer on the client:
      • Go to Printers & scanners
      • Select the shared printer > Remove
      • Restart the client PC
      • Add it again using the manual path above

    For error 0x00000709, there are two documented cases in the context:

    • If the printer is being accessed through a CNAME alias in DNS, this error can occur. In that case, use the actual host name instead of the CNAME in the UNC path. A documented workaround on older print-server scenarios is to implement the DnsOnWire registry value and add the CNAME to the local Hosts file as a NetBIOS name, then restart the Print Spooler service. This is a server-side workaround and involves registry changes, so use caution.
    • If the issue started after specific Windows updates in print server environments, 0x00000709 is also a known printer connection error. In the documented Windows 10 case, it was resolved in KB5007253.

    If this is a normal Windows 11 PC sharing a printer to other home or small-office clients, the most accurate supported fix from the context is to avoid auto-discovery and reconnect the printer manually using \\ComputerName\PrinterShareName after confirming sharing, network access, and credentials.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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