About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Two Microsoft pages describe the same fault with two messages. Clients that connect to a shared printer through a DNS alias (a CNAME record) get "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." or "Operation could not be completed (error 0x00000709)", while the same printer connects when the real host name is used. The documented fix is a registry value on the print server, DnsOnWire, followed by a restart of the Print Spooler service.
Test the real host name first, record the registry values you are about to change, and apply the fix on the print server only. Microsoft's pages describe Windows Server 2008 R2 print servers and Windows 7 clients. They do not say whether newer versions behave the same way, so treat the fix as something to test, not to assume.
What the error means
The 0x00000709 page (Windows Client, "Error 0x00000709 when you use CNAME record") describes the scenario: printers are hosted on a server running Windows Server 2008 R2, you give users an alternative UNC path built on a CNAME (alias) record in DNS, and clients try to connect by that alias. They cannot, and Microsoft's page says: "Attempts to connect to the printers succeed as long as you use the actual host name instead of the CNAME record."
The Windows Server page explains what a network trace shows. The client sends a RpcOpenPrinterEx request for a path such as \\printsvr\Microsoft XPS Document Writer, and the server answers with ERROR_INVALID_PRINTER_NAME. Microsoft gives the cause as "optimization changes to the spooler code for non-clustered computers". When the operating system loads, the Print Spooler service loads the local name of the computer and the other local names that are in the DNS cache. It uses those names to serve requests. To serve a request for a name such as an alias (CNAME) record, the service must gain access to the network and query for it, and Microsoft's page says "This behavior decreases the performance of the service."
A third page covers a case where the first fix is not enough: "This issue may occur if certain non-Microsoft DNS solutions are providing name resolution for the network", specifically a third-party DNS that "provides QRecord responses of type ALL".
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Print server does not resolve names for its aliases (spooler behaviour) | "Windows couldn't connect to the printer" by alias; real name works | Connect using the real host name; a trace shows ERROR_INVALID_PRINTER_NAME |
DnsOnWire is set but 0x00000709 persists with a non-Microsoft DNS |
"Operation could not be completed (error 0x00000709)" | Value is present; only the DNS provider or DNS administrator can say whether it returns QRecord answers of type ALL |
| Part of the combined fix is not applied | Microsoft's 0x00000709 page lists the case where the problem persists after the DnsOnWire registry value is implemented; the Windows Server 2012 R2 and Windows 7 SP1 page also sets DisableStrictNameChecking and OptionalNames |
reg query of DisableStrictNameChecking and OptionalNames |
| Load-balanced or round-robin alias | Some connections fail | Microsoft's page says load-balancing printers with Network Load Balancing (NLB) or DNS round robin "isn't supported" |
Prove the cause before changing anything
All of these read only. First, from a client that fails, connect to the printer using the print server's real host name instead of the alias. If that works and the alias does not, you are in the situation Microsoft describes.
Then, on the print server, record the current values:
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Print" /v DnsOnWire
reg query "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" /v DisableStrictNameChecking
reg query "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" /v OptionalNames
The reg query page documents /v valuename to query a single value. Write down which values are present and which are not. That record decides which back-out applies if you later need to undo the change.
Example (illustrative): at contoso.com.au the print server ps01 has a DNS alias printers.contoso.com.au, and staff have \\printers\Reception-MFP mapped through a logon script. After a server move, new laptops show "Windows couldn't connect to the printer". \\ps01\Reception-MFP works. All three reg query commands on ps01 report that the values are not found, so none of Microsoft's settings are in place.
Fix
Work on the print server only, in an elevated command prompt. Microsoft's pages recommend adding the registry key "on only the print servers that must be accessed by an alias (CNAME) resource record", because it decreases performance.
Step 1: save what is there. Export the two keys so you can restore them.
reg export "HKLM\SYSTEM\CurrentControlSet\Control\Print" C:\Temp\print-before.reg
reg export "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" C:\Temp\lanman-before.reg
The reg export page shows the form reg export keyname filename, and says the file must have a .reg extension. Create C:\Temp first if it does not exist.
Step 2: add the value.
Disruptive step: the next command changes how the spooler resolves names and Microsoft's pages say it reduces spooler performance.
reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1
This is the Microsoft command, shown for a server being accessed by an alias. Microsoft's pages add: "Some 3rd party DNS Providers require the use of QWord. Please remove the DWord if it exists." They give no command for the QWord form, so if your DNS provider needs it, use Microsoft support for the exact syntax rather than guessing.
To undo it: if DnsOnWire was absent in your earlier query, run reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Print" /v DnsOnWire /f, then restart the Print Spooler service. If it was present before, run the same reg add command again with /t and /d set to the type and data your earlier query showed, and add /f to overwrite the new value. The exported file records the whole key, so importing it would also overwrite any other setting changed under that key since the export; use it only if you want the whole key back as it was.
Step 3: the two server settings (for the combined fix).
Disruptive step: the two commands below write values under the LanmanServer service parameters, not under the print settings, so their effect may reach beyond printing; Microsoft's page does not describe it.
Microsoft's page for Windows Server 2012 R2 and Windows 7 SP1 lists two more commands as part of the resolution for both errors:
reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v DisableStrictNameChecking /t REG_DWORD /d 1
reg add hklm\system\currentcontrolset\services\lanmanserver\parameters /v OptionalNames /t REG_SZ /d "printers"
Microsoft's page prints the last value as " aliasname ", with spaces inside the quotes. Replace the placeholder with the alias your clients use; the example writes "printers" without spaces. After the command, run the third reg query and check that the value shows the alias exactly as your clients type it. Microsoft's page does not say whether to include the DNS domain suffix, and does not explain what each value does.
To undo them: if the values were absent, use reg delete with /v DisableStrictNameChecking /f and /v OptionalNames /f on that key. If they existed, run reg add on the same key with /f and the type and data your earlier reg query showed for each. Importing C:\Temp\lanman-before.reg restores the whole key and overwrites anything else changed under it since, so use it only if you want that.
Step 4: if 0x00000709 continues with a non-Microsoft DNS.
Save first: before you edit the Hosts file, save a copy of it.
Risk: the Hosts entry below is a fixed address on that server and does not follow DNS if the address changes. Remove the line if the address changes.
Microsoft's extra step is to edit the local Hosts file on the print server and add the alias, written as a NetBIOS name and not an FQDN. Its example: 192.168.0.10 CNAME is right and 192.168.0.10 CNAME.CONTOSO.COM is wrong. In the example, the line would be 10.0.20.15 printers. To undo it, put the saved copy back.
Step 5: restart the Print Spooler service, which Microsoft's pages say is needed for the entry to take effect.
Disruptive step: restarting the spooler interrupts printing for all users of the server while it restarts. Choose a quiet time. Back-out: none needed for the restart itself; the service starts again.
Confirm the fix
- From a client that failed, connect to
\\printers\Reception-MFPusing the alias. It should add the printer without an error. - Run the three
reg querycommands again; the values should match what you set. - Print a test page from a client that connected by alias.
What to watch afterwards
- Print server response. Microsoft's page says the registry key "decreases performance", so watch queue times on a busy server, and compare them with the figures you noted before the change.
- Any alias that is also served by NLB or DNS round robin. Microsoft's page says this "isn't supported" and that the workaround covers only one print server behind an alias.
- A change of print server address, if you used a Hosts entry.
Read next
Related articles you may want next.
- TroubleshootingPrinter driver will not download from the print server: Point and Print restrictions and event IDs 4098, 8192, 1111, 23, 22, 1, 215 and 808Events 4098, 8192, 1111, 23, 22, 1, 215 and 808 point to Point and Print Restrictions. Confirm in the logs, back up the GPO, test on a copy first.Read article
- TroubleshootingPrint Spooler Crashes on Remote Desktop Hosts: Driver ChecksPrint Spooler stops on a Remote Desktop host? Gather crash evidence, check spool files and driver isolation modes, and keep Point and Print protections on.Read article
- TroubleshootingWindows protected print mode and the end of servicing for third-party printer drivers: what a business should decideWindows protected print mode removes printers that need third-party drivers. Learn the dates, the options and what to check before you switch it on.Read article
Risks and limits
These commands have not been run or lab-tested.
The three pages name Windows Server 2008 R2, Windows Server 2012 R2 and Windows 7 and give no later version. Microsoft's three pages do not cover error 0x0000011b, so a client that shows that code needs a different diagnosis. Registry edits apply to the whole server, so compare each command with the output of your earlier reg query before you run it.
Sources
- Windows couldn't connect to the printer — Microsoft Learn, page dated 2026-02-12, accessed 20 November 2026
- Error 0x00000709 when you use CNAME record — Microsoft Learn, page dated 2026-02-12, accessed 20 November 2026
- Errors when you connect to a shared printer by using a CNAME record — Microsoft Learn, page dated 2026-02-12, accessed 20 November 2026
- reg query — Microsoft Learn, page dated 2023-02-03, accessed 20 November 2026
- reg export — Microsoft Learn, page dated 2023-02-03, accessed 20 November 2026
- reg import — Microsoft Learn, page dated 2023-02-03, accessed 20 November 2026
- reg add — Microsoft Learn, page dated 2024-01-04, accessed 20 November 2026
- reg delete — Microsoft Learn, page dated 2023-02-03, accessed 20 November 2026
This article was originally published on .