Friday, April 27, 2012 8:31 PM
I am running a print server on a 2 node failover cluster running Windows Server 2008R2 Enterprise Edition. I had installed and shared 12 - 15 printers and shared them on users’ desktops. Each of the printers is working as expected.
Four or five weeks elapsed without incident and I needed to install another printer. I was able to install it on the print server but when I attempted to install it as a shared printer I received a "Windows cannot contact printer error". I have investigated and determined that the print server name is incorrect in active directory; for some reason the name has been truncated by 1 character. For example, the print server name is xyzprintserver01 but the CN in active directory is xyzprintserver0. I can manually enter the print server name and install the printer without error. If I attempt to select the printer from the drop down list however, I receive the "cannot connect" error since the print server name is incorrect.
Now I am trying to determine the best way to correct the name issue in Active Directory and how to prevent a reoccurrence. Any ideas how to do this?
Thank you in advance
- Edited by SilverNickel Friday, April 27, 2012 8:32 PM
Sunday, April 29, 2012 3:31 AM
from memory there is a 15 character limit (same as for NETBIOS) for cluster object names.
I haven't found any specific statement on this in formal documentation after a quick search of TN Library, but there is this:
Monday, May 07, 2012 4:29 PM
Sorry for my delay in responding but I have been out for the last week due to an unexpected emergency. I had considered the name length but discarded the thought because the print services initially worked. I'll rename it to a shorter name and see if that resolves the issue.