Fix Printer Sharing Error 0x000006D9 on Windows Server: A Comprehensive Guide

Table of Contents

Encountering errors when performing seemingly straightforward tasks like sharing a printer can be incredibly frustrating. One such persistent issue that Windows users, particularly those on Windows 7 Service Pack 1 and Windows Server 2008 R2, often face is Error Code 0x000006D9. This error prevents the successful sharing of printers and can disrupt essential network operations. This comprehensive guide will delve into the symptoms, underlying cause, and a precise resolution for this vexing printer sharing problem, along with advanced insights and troubleshooting tips applicable to various Windows environments.

Understanding the Symptoms of Error 0x000006D9¶

When attempting to share a printer, you might encounter distinct error messages depending on the method you employ. Recognizing these specific messages is the first step in diagnosing the problem. This error clearly indicates a failure in the printer sharing process, often pointing towards a deeper system configuration issue.

Error Messages You Might See¶

If you are utilizing the Add Printer Wizard to configure a shared printer on your network, the following error message will typically appear:

Windows could not share your printer. Operation could not be completed (Error 0x000006D9)

Alternatively, if your attempt to share the printer is made through the Printer Properties dialog, you will likely encounter this message:

Printer Settings could not be saved. Operation could not be completed (Error 0x000006D9)

These messages directly confirm the presence of the 0x000006D9 error, preventing the system from saving the sharing configuration or completing the sharing operation. Both messages indicate the same underlying issue, regardless of the user interface path taken.

Deciphering the Error Code¶

For those who prefer a more technical insight, looking up the error code 0x000006D9 reveals its root cause. Using the err.exe utility (a Windows command-line tool for looking up error codes), the output provides critical information:

C:\>err.exe 0x000006d9
for hex 0x6d9 / decimal 1753
EPT_S_NOT_REGISTERED winerror.h
There are no more endpoints available from the endpoint mapper.

The output EPT_S_NOT_REGISTERED indicates that the Endpoint Mapper Service, which helps clients locate services on the network, cannot find or register the necessary endpoints for printer sharing. This is a crucial clue that points directly to network communication issues, often related to services that manage network access, such as a firewall. Essentially, the system is unable to properly expose the printer sharing service to other devices on the network.

The Root Cause: Windows Firewall Service Dependency¶

The primary reason behind the 0x000006D9 printer sharing error is a dependency on the Windows Firewall Service. Many modern Windows functions, especially those involving network communication and resource sharing, rely heavily on the firewall service to properly manage network traffic and security. Disabling or stopping this service, while seemingly a way to troubleshoot network issues, often leads to other problems due to these intricate dependencies.

Why Windows Firewall is Critical for Printer Sharing¶

Printer sharing in Windows 7 and Windows Server 2008 R2, as well as subsequent Windows versions, is not merely about enabling a toggle switch. It involves several underlying network protocols and services that must communicate effectively and securely across the network. The Windows Firewall acts as a gatekeeper, ensuring that these communications are allowed while protecting the system from unauthorized access.

The Spooler service, which manages print jobs and printer sharing, has a direct dependency on the Windows Firewall Service. Specifically, the Spooler service uses the Firewallapi.dll file to make API calls to check the availability and status of the Windows Firewall service. If the firewall service is not running or is disabled, these API calls fail, preventing the Spooler service from properly configuring and announcing the shared printer on the network. This dependency ensures that printer sharing, when enabled, automatically configures the necessary firewall rules to allow legitimate network traffic.

If the Windows Firewall Service is stopped or set to a disabled state, the system cannot establish the necessary network endpoints or register them with the Endpoint Mapper. This results in the EPT_S_NOT_REGISTERED error, as the system perceives a lack of available communication channels for the printer sharing function. Therefore, maintaining an active and correctly configured Windows Firewall Service is paramount for successful printer sharing.

Resolution: Enabling and Starting the Windows Firewall Service¶

Fortunately, the resolution for error 0x000006D9 is often straightforward: ensure the Windows Firewall Service is set to start automatically and is currently running. This simple action allows the Spooler service to correctly interact with the firewall API and establish the necessary communication channels for printer sharing.

Step-by-Step Guide to Re-enabling Windows Firewall¶

Follow these detailed steps to resolve the issue on your Windows system:

1. Access Services Management Console:

   • Press the Windows key + R to open the Run dialog box.
   • Type services.msc and press Enter, or click OK. This will open the Services management console, which lists all services installed on your system.

   

2. Locate Windows Firewall Service:

   • In the Services window, scroll down the list until you find the service named Windows Firewall. The services are typically listed alphabetically.

3. Check Service Status and Startup Type:

   • Double-click on the Windows Firewall service to open its Properties dialog box.
   • In the General tab, observe the Startup type and Service status.
   • If the Startup type is set to Disabled or Manual, and the Service status is Stopped, this is the cause of your error.

   

4. Set Startup Type to Automatic:

   • From the Startup type drop-down menu, select Automatic. This ensures that the Windows Firewall Service starts automatically every time your system boots up.

5. Start the Service:

   • Click the Start button if the Service status is currently Stopped. This will immediately initiate the Windows Firewall Service.
   • Wait a few moments for the service to start. You should see the Service status change to Running.

6. Apply Changes and Exit:

   • Click Apply and then OK to save your changes and close the Properties dialog box.
   • Close the Services management console.

After completing these steps, attempt to share your printer again. The error 0x000006D9 should now be resolved, and you should be able to successfully share the printer. It is generally recommended to restart your computer after making significant service configuration changes, though it might not be strictly necessary in this particular case for the fix to take effect.

Deep Dive into Firewall Mechanics for Printer Sharing¶

The interaction between the Spooler service and the Windows Firewall is more intricate than simply starting the service. When printer sharing is initiated for the first time, or when new network services are exposed, the Windows Firewall dynamically creates and enables a specific set of incoming rules. These rules are crucial for allowing network traffic related to file and printer sharing to pass through the firewall, enabling other devices on the network to discover and connect to the shared resource.

Essential Incoming Firewall Rules¶

The following table details the key incoming firewall rules that are enabled when you share a printer (or a folder) for the first time. Each rule serves a specific purpose in facilitating network communication for shared resources:

Rule Name	Protocol/Service	Description
File and Printer Sharing (Spooler Service - RPC-EPMAP)	RPC-EPMAP	This rule allows incoming remote procedure call (RPC) endpoint mapper traffic. The RPC endpoint mapper helps client applications locate RPC services (like the Spooler service) on the server by providing their port numbers.
File and Printer Sharing (Spooler Service - RPC)	RPC	This rule permits general incoming RPC traffic specifically for the Spooler service. Once the client knows the port via EPMAP, this rule allows direct communication with the Spooler service to manage print jobs and settings.
File and Printer Sharing (Echo Request - ICMPv4-In)	ICMPv4	Allows incoming ICMP (Internet Control Message Protocol) echo requests for IPv4. This is commonly known as “ping” and helps with basic network connectivity testing and discovery. While not directly for sharing, it aids in network visibility.
File and Printer Sharing (Echo Request - ICMPv6-In)	ICMPv6	Similar to the ICMPv4 rule, but for IPv6 traffic. Essential for networks that use IPv6 or dual-stack configurations, allowing connectivity testing.
File and Printer Sharing (LLMNR-UDP-In)	LLMNR (UDP)	Enables incoming Link-Local Multicast Name Resolution (LLMNR) traffic over UDP. LLMNR allows hosts on the same local network segment to perform name resolution for other hosts without requiring a DNS server, critical for network discovery in workgroup environments.
File and Printer Sharing (NB-Datagram-In)	NetBIOS (UDP)	Allows incoming NetBIOS over TCP/IP (NBT) datagram traffic. NetBIOS datagrams are used for connectionless communication and for broadcasting information within a local network, often used for browsing network resources.
File and Printer Sharing (NB-Name-In)	NetBIOS (UDP)	Permits incoming NetBIOS name resolution traffic over UDP. This rule enables hosts to resolve NetBIOS names to IP addresses, which is fundamental for finding other computers and shared resources on a NetBIOS-enabled network.
File and Printer Sharing (NB-Session-In)	NetBIOS (TCP)	Allows incoming NetBIOS session service traffic over TCP. NetBIOS sessions are used for reliable, connection-oriented communication between two hosts, essential for transferring larger amounts of data during file and print sharing operations.
File and Printer Sharing (SMB-In)	SMB (TCP)	This rule is critical as it enables incoming Server Message Block (SMB) traffic over TCP. SMB is the core protocol used for file sharing, printer sharing, and other network communication between Windows computers. This is the primary protocol for the actual data transfer.

It’s important to note that these same incoming rules are also enabled when you share a folder on the computer for the first time. This demonstrates the integrated nature of file and printer sharing within Windows.

Registry Location of Firewall Rules¶

When the Windows Firewall Service is running and these rules are active, their configurations are stored in the system registry. You can inspect these rules by navigating to the following registry path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules

This registry key contains a collection of values, each representing a specific firewall rule, detailing its parameters such as name, action (allow/block), direction (inbound/outbound), and associated protocols or applications. Directly modifying these registry entries is generally not recommended unless you are an advanced user with a clear understanding of the firewall’s inner workings.

Event Logging for Firewall Changes¶

Windows also provides robust event logging for firewall activity. When a firewall rule is modified or created, similar events are logged in the Applications and Services Logs under the Microsoft-Windows-Windows Firewall With Advanced Security/Firewall log. These logs are invaluable for auditing firewall changes and troubleshooting network connectivity issues.

Below are examples of Event ID 2005 entries you might observe when printer sharing rules are enabled:

Log Name: Microsoft-Windows-Windows Firewall With Advanced Security/Firewall
Source: Microsoft-Windows-Windows Firewall With Advanced Security
Date: <Date>
Event ID: 2005
Task Category: None
Level: Information
Keywords: (2199023255552)
User: LOCAL SERVICE
Computer: <ComputerName>
Description: A rule has been modified in the Windows Firewall exception list.
Modified Rule:
Rule ID: FPS-SpoolSvc-In-TCP-NoScope
Rule Name: File and Printer Sharing (Spooler Service - RPC)
Origin: Local
Active: Yes
Direction: Inbound
Profiles: Domain
Action: Allow
Application Path: C:\Windows\system32\spoolsv.exe
Service Name: Spooler
Protocol: TCP
Security Options: None
Edge Traversal: None
Modifying User: SYSTEM
Modifying Application: C:\Windows\System32\svchost.exe

This event clearly shows the FPS-SpoolSvc-In-TCP-NoScope rule being modified (or created) to allow inbound TCP traffic for the spoolsv.exe application (the Spooler service).

Another example related to the RPC Endpoint Mapper:

Log Name: Microsoft-Windows-Windows Firewall With Advanced Security/Firewall
Source: Microsoft-Windows-Windows Firewall With Advanced Security
Date: <Date>
Event ID: 2005
Task Category: None
Level: Information
Keywords: (2199023255552)
User: LOCAL SERVICE
Computer: <ComputerName>
Description: A rule has been modified in the Windows Firewall exception list.
Modified Rule:
Rule ID: FPS-RPCSS-In-TCP-NoScope
Rule Name: File and Printer Sharing (Spooler Service - RPC-EPMAP)
Origin: Local
Active: Yes
Direction: Inbound
Profiles: Domain
Action: Allow
Application Path:
Service Name: Rpcss
Protocol: TCP
Security Options: None
Edge Traversal: None
Modifying User: SYSTEM
Modifying Application: C:\Windows\System32\svchost.exe

This event confirms the configuration of the FPS-RPCSS-In-TCP-NoScope rule, allowing inbound TCP traffic for the RPCSS (Remote Procedure Call (RPC) Locator) service, which is vital for the RPC-EPMAP function. Monitoring these logs can provide valuable insights into whether the firewall rules for printer sharing are being correctly applied.

Visualizing the Printer Sharing Process with Firewall¶

To better understand the interaction, consider this simplified Mermaid diagram:

mermaid graph TD A[User Initiates Printer Share] --> B{Windows Spooler Service} B -- Calls --> C[Firewallapi.dll] C -- Checks Status --> D{Windows Firewall Service} D -- Is Running? --> E{Yes} E --> F[Dynamically Creates/Enables Firewall Rules] F --> G[Registers Endpoints with Endpoint Mapper] G --> H[Printer Shared Successfully] D -- Is Stopped/Disabled? --> I{No} I --> J[API Call Fails] J --> K[Endpoint Mapper Cannot Register Service] K --> L[Error 0x000006D9] L --> M[Printer Sharing Fails]

This diagram illustrates the critical path: if the Windows Firewall Service is not running, the entire process of setting up and registering the shared printer fails, leading to the 0x000006D9 error.

Advanced Troubleshooting and Common Pitfalls¶

While enabling the Windows Firewall Service is the primary fix, sometimes the error might persist or similar issues arise due to other factors. Here’s a look at some advanced troubleshooting steps and common pitfalls.

1. Group Policy Object (GPO) Conflicts¶

In domain-joined environments, Group Policy Objects (GPOs) can override local service settings and firewall rules. If your Windows Firewall service keeps reverting to Disabled or Stopped, or if custom firewall rules are missing, a GPO might be enforcing these settings.

• How to Check for GPO Enforcement:
  • Open an elevated Command Prompt and type gpresult /r. Look for “Applied Group Policy Objects” and “Filtering by GPO”.
  • Use the GPMC.msc (Group Policy Management Console) on a domain controller to review GPOs linked to your computer’s Organizational Unit (OU) that might affect Firewall settings (Computer Configuration > Policies > Windows Settings > Security Settings > Windows Firewall with Advanced Security).
• Resolution: Adjust the GPO that is enforcing the firewall settings or apply a new GPO to correctly configure the Windows Firewall Service to Automatic and ensure it’s running.

2. Third-Party Firewall or Security Software¶

Some third-party antivirus suites or security software include their own firewall components. These can sometimes interfere with or completely disable the Windows Firewall.

• Symptoms: Even if you set Windows Firewall to Automatic and Running, the error persists, or Windows Firewall might report that it’s being managed by another application.
• Resolution:
  • Temporarily disable the third-party firewall/security software to see if the error resolves.
  • If it does, consult the documentation for your third-party software to configure exceptions for file and printer sharing, or to allow Windows Firewall to manage these rules.
  • Consider completely uninstalling conflicting third-party firewalls if they are not essential or if they frequently cause issues.

3. Network Discovery Settings¶

For printer sharing to work across a network, network discovery must be enabled. This allows your computer to see other devices on the network and be seen by them.

• How to Check:
  • Go to Control Panel > Network and Sharing Center.
  • Click on Change advanced sharing settings.
  • Expand your current profile (usually Private or Domain) and ensure Turn on network discovery is selected, and Turn on file and printer sharing is also enabled.

4. Printer Driver Issues¶

While less directly related to 0x000006D9 (which is a network communication error), an outdated or corrupted printer driver can cause sharing problems.

• Resolution:
  • Ensure your printer driver is up-to-date. Visit the printer manufacturer’s website to download the latest drivers for your operating system.
  • Try reinstalling the printer driver.

5. SMB 1.0/CIFS File Sharing Support (Older Devices)¶

If you are trying to share a printer with very old operating systems (like Windows XP) or certain legacy network devices, they might rely on SMB 1.0. Newer Windows versions often have SMB 1.0 disabled by default for security reasons.

• Consideration: Enabling SMB 1.0 is generally not recommended due to security vulnerabilities but might be a last resort for specific legacy compatibility needs.
• How to Check/Enable (Use with caution):
  • Go to Control Panel > Programs and Features > Turn Windows features on or off.
  • Scroll down and check if SMB 1.0/CIFS File Sharing Support is enabled. If not, enable it and restart your system.

6. File and Printer Sharing Role (Windows Server Specific)¶

On Windows Server operating systems, ensure that the “File and Storage Services” role (specifically, “File Server” and “Server for NFS” if needed, though “File Server” is usually enough for SMB-based sharing) is installed and correctly configured. While typically this would be installed for general file sharing, its components are crucial for printer sharing as well.

Verifying Printer Sharing Functionality¶

After implementing the resolution and checking for advanced issues, it’s crucial to verify that printer sharing is now fully functional.

1. On the Server/Host Computer:

   • Go to Control Panel > Devices and Printers.
   • Right-click on the shared printer, select Printer properties, and then the Sharing tab. Confirm that the printer is marked as shared.
   • Try to print a test page locally.

2. On a Client Computer:

   • Method 1: Network Discovery: Open File Explorer, navigate to Network, and see if the host computer appears. Double-click on it to see the shared printer.
   • Method 2: Add Printer Wizard:
     • Go to Control Panel > Devices and Printers.
     • Click Add a printer.
     • Choose Add a network, wireless or Bluetooth printer.
     • The wizard should now be able to discover the shared printer. If not, select The printer that I want isn't listed and then Select a shared printer by name and type \\<HostComputerName>\<ShareName>.
   • Method 3: Direct UNC Path: Press Windows key + R, type \\<HostComputerName> (replace with the actual computer name or IP address of the host), and press Enter. You should see the shared printer listed. Double-click to install it.
   • Test Print: Once the printer is installed on the client, try printing a test page from an application like Notepad.

If you can successfully install and print to the shared printer from a client machine, your issue is resolved!

Preventative Measures and Best Practices¶

To avoid encountering the 0x000006D9 error or similar printer sharing problems in the future, adhere to these best practices:

• Maintain Windows Firewall: Do not disable the Windows Firewall unless you have a robust third-party alternative that you fully understand and manage. The Windows Firewall is a critical security component.
• Regular Updates: Keep your Windows operating system and printer drivers updated. Updates often include fixes for network and sharing components.
• Understand Network Profiles: Be aware of your network profile (Public, Private, Domain). Firewall rules can differ significantly between profiles, and incorrect profiling can block necessary traffic.
• Centralized Management: In business environments, use Group Policy to centrally manage Windows Firewall settings, ensuring consistency and proper configuration across all devices.
• Document Configurations: Keep a record of your network configurations, especially custom firewall rules or service settings, to aid in future troubleshooting.

By understanding the vital role of the Windows Firewall in network services like printer sharing and following these guidelines, you can ensure a smoother and more reliable computing experience.

---

Have you encountered the 0x000006D9 error, or do you have additional tips for troubleshooting printer sharing issues on Windows Server? Share your experiences and insights in the comments below! Your contributions can help others in the community resolve their own technical challenges.