Cannot Publish a Printer to Active Directory from a Cluster in a Child Domain (286254)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q286254 SYMPTOMS
If you have a cluster in a child domain and the Cluster Service account exists in the parent domain, you cannot publish to Active Directory a printer that is shared on the cluster virtual node. The following event will be posted to the System event log:
Event ID 38
Source: Print
PrintQueue printer CN name was successfully deleted from container LDAP://container CAUSE
When the client uses the domain controller to decipher the GUID of the Cluster Service account, it does not specify the global catalog server in particular. Instead, the closest domain controller is used. If the cluster is in the parent domain, it is likely that the global catalog server will be the domain controller that is contacted. In a child domain, this is usually not the case. In this scenario, only the global catalog server is guaranteed to know how to decipher the GUID, so the printer is not published.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
2/21/2001 03:40p 5.0.2195.3287 246,032 Localspl.dll STATUSMicrosoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbprint kbWin2000PreSP2Fix kbWin2000PreSP3Fix kbWin2000sp3fix KB286254 |
---|
|