Windows cannot find the printer in Active Directory
You searched for a printer in the directory rather than on the local network, and the directory returned nothing. Either the queue was never published to Active Directory, the entry is stale, or your PC cannot query the directory at that moment. It is a lookup failure, so the printer may be running perfectly well.
What causes it
- The shared queue was never published to the directory by the print server
- The published object is stale after the server or queue was renamed
- The PC has lost its domain trust relationship or is off the corporate network without VPN
- You are signed in with a local or Microsoft account rather than a domain account
- Directory replication has not yet carried the new printer to your site
How to fix it, in order
Work down the list and stop when the printer recovers. The steps are ordered from most likely and least invasive to last resort.
Confirm you are on the domain network
Check that the PC is connected to the corporate network or an active VPN, then open a command prompt and run whoami to confirm you are signed in with a domain account rather than a local one. Directory searches only work from a domain session with a route to a domain controller.
Add the printer by its share path instead
Open Settings › Bluetooth & devices › Printers & scanners › Add device › Add manually, choose Select a shared printer by name, and type \\printserver\queuename. This skips the directory entirely and works even for queues that were never published.
Browse the print server directly
In File Explorer type \\printserver and press Enter to see the queues it offers. Double-clicking a printer there installs it. This also confirms whether the server is reachable at all, which the directory search does not tell you.
Ask whether the queue is published
On the print server, a queue is published through its properties on the Sharing tab, where List in the directory must be ticked. If the administrator has not ticked it, the printer will never appear in a directory search no matter what the client does.
Try adding it by IP
If you know the device's address, use Add manually › Add a printer using an IP address or hostname with Device type set to TCP/IP Device. Direct printing bypasses both the directory and the print server, though it also bypasses any server-side accounting your organisation relies on.
Restart the Print Spooler
Press Windows+R, type services.msc, press Enter and restart Print Spooler. Cached directory results can persist after a printer is republished, and a spooler restart forces a fresh query.
Check the machine's domain trust
If other domain resources are also unreachable, the computer account may have lost its trust relationship. That shows up as sign-in and share access problems more broadly, and needs an administrator to rejoin the machine rather than any printer-side change.
Stopping it happening again
When it is not worth fixing yourself
If you would rather not work through this alone, a printer specialist can take a look with you on a screen-share and tell you honestly whether the machine is worth saving.
Frequently asked questions
Why can a colleague find it and I cannot?
They may be at a different site where directory replication has completed, or they may already have the queue installed from before.
Is adding by IP acceptable at work?
Sometimes, but it bypasses print accounting, secure release and driver management. Check with IT before doing it on a corporate device.
Does this happen at home?
No. Active Directory searching only applies to domain-joined machines in a managed network.
Questions & comments (0)
No comments yet. Describe your printer model, operating system and the exact message you see; comments appear after review.
Ask about this page
Your comment appears after our team approves it. Or sign in to post faster.