Quantcast
Channel: Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server
Viewing all 12 articles
Browse latest View live

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This worked for us in our test environment and we plan on replicating it in our production environment.

1) Add A record or CNAME to DNS

2) Add the following to the registry:

Windows Registry Editor Version 5.00
;Print Spooler Driver Exception
[ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"ThrowDriverException"=dword:00000001

;Disabled Strict Name Checking for Win2k8R2
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"DisableStrictNameChecking"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Lsa]
"DisableLoopbackCheck"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"DnsOnWire"=dword:00000001

-------------------------------
3) open admin console and enter:
NETDOM COMPUTERNAME [fqdn of server you are on] /add:[fqdn of dns entry (from step 1) to accept]

*Note* We were confused a little about the "computername" but it should be typed as is, "NETDOM COMPUTERNAME" ....

Source:
- Windows Printer/Fax Technet
- http://www.marc-lognoul.me/itblog-en/post/2010/09/08/Multiple-Names-for-a-File-and-Print-Server-Running-Windows-Server-2008-R2.aspx


Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This (KB979602) did not work for me, but KB2546625 addresses what to do if this doesn't work. I had to reboot before the fix took effect.

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

Symptom

 

When you connect to a printer on printer server via CNAME,  you receive the following error message:

"Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to network."

 

If you connect to the print server via the server name itself, it works properly. Meanwhile, you can access the file share on the printer server via CNAME properly.

 

Cause

 

The printer server is not configured to accept requests via CNAME connection.

 

Resolution

 

Run the following command line to add the registry value for CNAMEs to work on the printer server:

 

reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1

 

Applies to

 

Windows Server 2008 R2

 

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This worked for us in our test environment and we plan on replicating it in our production environment.

1) Add A record or CNAME to DNS

2) Add the following to the registry:

Windows Registry Editor Version 5.00
;Print Spooler Driver Exception
[ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"ThrowDriverException"=dword:00000001

;Disabled Strict Name Checking for Win2k8R2
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"DisableStrictNameChecking"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Lsa]
"DisableLoopbackCheck"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"DnsOnWire"=dword:00000001

-------------------------------
3) open admin console and enter:
NETDOM COMPUTERNAME [fqdn of server you are on] /add:[fqdn of dns entry (from step 1) to accept]

*Note* We were confused a little about the "computername" but it should be typed as is, "NETDOM COMPUTERNAME" ....

Source:
- Windows Printer/Fax Technet
- http://www.marc-lognoul.me/itblog-en/post/2010/09/08/Multiple-Names-for-a-File-and-Print-Server-Running-Windows-Server-2008-R2.aspx

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This (KB979602) did not work for me, but KB2546625 addresses what to do if this doesn't work. I had to reboot before the fix took effect.

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

Symptom

 

When you connect to a printer on printer server via CNAME,  you receive the following error message:

"Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to network."

 

If you connect to the print server via the server name itself, it works properly. Meanwhile, you can access the file share on the printer server via CNAME properly.

 

Cause

 

The printer server is not configured to accept requests via CNAME connection.

 

Resolution

 

Run the following command line to add the registry value for CNAMEs to work on the printer server:

 

reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1

 

Applies to

 

Windows Server 2008 R2

 

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This worked for us in our test environment and we plan on replicating it in our production environment.

1) Add A record or CNAME to DNS

2) Add the following to the registry:

Windows Registry Editor Version 5.00
;Print Spooler Driver Exception
[ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"ThrowDriverException"=dword:00000001

;Disabled Strict Name Checking for Win2k8R2
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"DisableStrictNameChecking"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Lsa]
"DisableLoopbackCheck"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"DnsOnWire"=dword:00000001

-------------------------------
3) open admin console and enter:
NETDOM COMPUTERNAME [fqdn of server you are on] /add:[fqdn of dns entry (from step 1) to accept]

*Note* We were confused a little about the "computername" but it should be typed as is, "NETDOM COMPUTERNAME" ....

Source:
- Windows Printer/Fax Technet
- http://www.marc-lognoul.me/itblog-en/post/2010/09/08/Multiple-Names-for-a-File-and-Print-Server-Running-Windows-Server-2008-R2.aspx

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This (KB979602) did not work for me, but KB2546625 addresses what to do if this doesn't work. I had to reboot before the fix took effect.


Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

Symptom

 

When you connect to a printer on printer server via CNAME,  you receive the following error message:

"Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to network."

 

If you connect to the print server via the server name itself, it works properly. Meanwhile, you can access the file share on the printer server via CNAME properly.

 

Cause

 

The printer server is not configured to accept requests via CNAME connection.

 

Resolution

 

Run the following command line to add the registry value for CNAMEs to work on the printer server:

 

reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1

 

Applies to

 

Windows Server 2008 R2

 

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This worked for us in our test environment and we plan on replicating it in our production environment.

1) Add A record or CNAME to DNS

2) Add the following to the registry:

Windows Registry Editor Version 5.00
;Print Spooler Driver Exception
[ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"ThrowDriverException"=dword:00000001

;Disabled Strict Name Checking for Win2k8R2
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"DisableStrictNameChecking"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Lsa]
"DisableLoopbackCheck"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print]
"DnsOnWire"=dword:00000001

-------------------------------
3) open admin console and enter:
NETDOM COMPUTERNAME [fqdn of server you are on] /add:[fqdn of dns entry (from step 1) to accept]

*Note* We were confused a little about the "computername" but it should be typed as is, "NETDOM COMPUTERNAME" ....

Source:
- Windows Printer/Fax Technet
- http://www.marc-lognoul.me/itblog-en/post/2010/09/08/Multiple-Names-for-a-File-and-Print-Server-Running-Windows-Server-2008-R2.aspx

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

This (KB979602) did not work for me, but KB2546625 addresses what to do if this doesn't work. I had to reboot before the fix took effect.

Forum FAQ: Cannot connect and print to printers via CNAME alias of printer server

$
0
0

Symptom

 

When you connect to a printer on printer server via CNAME,  you receive the following error message:

"Windows cannot connect to the printer. Make sure that you have typed the name correctly, and that the printer is connected to network."

 

If you connect to the print server via the server name itself, it works properly. Meanwhile, you can access the file share on the printer server via CNAME properly.

 

Cause

 

The printer server is not configured to accept requests via CNAME connection.

 

Resolution

 

Run the following command line to add the registry value for CNAMEs to work on the printer server:

 

reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1

 

Applies to

 

Windows Server 2008 R2

 

Viewing all 12 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>