"Operation could not be completed (error 0x00000709)" error when you use a CNAME record for a print server in Windows Server 2008 R2

Article ID: 2546625 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Consider the following scenario:
  • You have printers that are hosted on a system that is running Windows Server 2008 R2.
  • You have to provide an alternative UNC path for the print server, and you decide to do this by using a CNAME (alias) resource record in DNS.
  • Clients try to connect to the printers by using the CNAME record in the UNC path.
In this scenario, you discover that clients cannot connect to the printers if they use the CNAME record in the UNC path. Additionally, attempts to connect to the shared printers fail with the following error:
Operation could not be completed (error 0x00000709). Double check the printer name and make sure that the printer is connected to the network.
Notes
  • Attempts to connect to the printers succeed as long as you use the actual host name instead of the CNAME record. 
  • After you implement the DnsOnWire registry value that is described in the following article in the Microsoft Knowledge Base, the problem persists:
    979602 Error message when you try to connect to a printer by using an alias (CNAME) resource record: "Windows couldn't connect to the printer"

Cause

This issue may occur if certain non-Microsoft DNS solutions are providing name resolution for the network.

Resolution

To work around this issue, follow these steps on the print server, and then restart the Print Spooler service:
  1. Implement the DnsOnWire registry value that is described in the following article in the Microsoft Knowledge Base:
    979602 Error message when you try to connect to a printer by using an alias (CNAME) resource record: "Windows couldn't connect to the printer" 
  2. Edit the local Hosts file to include the CNAME record for the server. 

    Note The Hosts file entry must be entered as a NetBIOS name instead of as an FQDN.

The following example is for illustration only. You will have to use names and IP addresses that are valid for your network.

Use NetBIOS name: 192.168.0.10 CNAME 

Don’t use FQDN: 192.168.0.10 CNAME.CONTOSO.COM

More information

The issue that is described in the "Symptoms" section may occur if the non-Microsoft DNS solution provides QRecord responses of type ALL.

Properties

Article ID: 2546625 - Last Review: February 1, 2013 - Revision: 5.0
Applies to
  • Windows Server 2012 Standard
  • Windows Server 2012 Essentials
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Standard without Hyper-V
Keywords: 
KB2546625

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com