Event ID 33 — AD DS Printer Publishing

Updated: November 30, 2007

Applies To: Windows Server 2008

red

You can publish printer information to Active Directory Domain Services (AD DS) so that users can search for printers by location or other attributes. Publishing a printer creates a PrintQueue object in AD DS as a child of the print server computer account.

Event Details

Product: Windows Operating System
ID: 33
Source: Microsoft-Windows-PrintSpooler
Version: 6.0
Symbolic Name: MSG_CANT_GET_DNS_DOMAIN_NAME
Message: While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: %1. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.

Resolve

Troubleshoot connectivity with a domain controller

To troubleshoot connectivity with a domain controller:

  1. On the print server, open the Command Prompt window, and then type ipconfig /all at the command prompt.
  2. Make sure that the print server has an IP address in the correct IP address range, and that it does not have an Automatic Private IP Addressing (APIPA) address (an IP address in the 169.254.x.x range).
  3. Ping the loopback address of 127.0.0.1 to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with the network adapter.
  4. Test whether you can ping the local IP address. If you can ping the loopback address but not the local IP address, there may be an issue with either the routing table or the network adapter driver.
  5. Ping the DNS servers. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or possibly a network problem between the print server and the DNS servers. It can also mean that the DNS servers are not configured to respond to ping requests. To determine if this is the case, ping the DNS servers from a computer that you know is functioning properly on the network.
  6. At the command prompt, type nslookupprint_server_name, where print_server_name is the computer name of the print server, and then press ENTER.
  7. If the nslookup command fails but you can ping or otherwise access the DNS server, restart the DNS Server service on the DNS server. To do this, open the Services snap-in from the Administrative Tools folder, select the DNS Server service, and then click the Restart Service toolbar button.
  8. On a domain controller in the same domain as the print server, type the following command at the command prompt: dcdiag /test:connectivity. If there are any errors, see Active Directory Operations Overview: Troubleshooting Active Directory-Related DNS Problems (http://go.microsoft.com/fwlink/?LinkID=57927) for further troubleshooting steps.
  9. Retry publishing the printer.

Verify

To verify that the printer was successfully published or removed from AD DS, do the following:

  • If the print server logs spooler information events, open Event Viewer and look for Print Spooler Event 36 (when publishing a printer), Print Spooler Event 38 (when removing a printer from AD DS), or Print Spooler Event 40 (when updating a printer).
  • Search AD DS for the printer by using the following procedure:
    1. Open the Printers folder on a computer in the same domain as the print server, and then click Add a printer. The Add Printer Wizard appears.
    2. Select A printer that is not attached to my computer (a network printer), and then click Next.
    3. Click The printer I am looking for is not on this list.
    4. Select Find a printer in Active Directory, based on location or feature, click Next, and then use the Find Printers dialog box to search AD DS for the printer.

Related Management Information

AD DS Printer Publishing

Printing Infrastructure

Community Additions

ADD
Show: