Link to home
Start Free TrialLog in
Avatar of First Last
First LastFlag for United States of America

asked on

Problem installing printers on new print server (2008R2)

I've recently setup a new print server (2008 R2) which has been joined to my domain and has the print server role installed.  I'm having a problem installing the shared printers on my clients.  From the devices and printers dialog on a windows 7 machine I'll click Add a Printer.  I select Add a Network Printer and it says no printers were found.  That is problem one.  So next I select The Printer that I want isn't listed and choose Find a printer in the directory based on location or feature and click next.  I can now see the list of all the printers on both the old and new print servers.  I double click one of the new shared printers and it will say connecting to the printer name on printserver.  Ultimately it will come back with an error stating Windows couldn't connect to the printer. Check the printer name and try again.  The name is correct.  If I cancel out of that and use the Select a shared printer by name option I can use a UNC path to see and install the printer:

\\printserver\printername

Once I enter the \\printerserver\ portion the printer shares all show up in the list and I can select them to install.  They install normally after clicking on them.

What am I doing wrong here that would cause the install to fail when using the first two options?  I would very much appreciate any assistance!
Avatar of Carlisle_Agent
Carlisle_Agent
Flag of United States of America image

It's not an issue between 64 and 32 bit is it?

i.e. if you have the server installed as 64 bit, and have installed a printer, but default it will only have 64 bit drivers, so when you try to connect to it a PC won't automatically install

If it is that, you just need to install the 32 bits drivers within the printer properties

Wayne
Avatar of First Last

ASKER

@Carlisle_Agent - nothing specific there to help and very broad (its for server 2003, I'm on 2008)

@WayneATaylor - Its not a 64/32bit problem as I have both instances of the drivers installed and I get the same issue on 32bit and 64bit machines.
Avatar of X Layer
Go to Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> Print Service -> Admin. Look there for errors and report back.
Ok, an interesting event listed there which occurs about every 2 hours:

The print queue could not be found on domain domain.local.  It may have been deleted from the Active Directory directory service. Windows will attempt to republish the print queue.  Error: 2116

Do you think this relates to the publishing problem?
Ok, I checked both links but found nothing useful there.  The MS article just says to wait for the print queue to republish the printers (it hasn't) while the Event ID site offers 4 suggestions which don't really solve anything.  I can get them to show up by checking the List in Directory option again but they disappear after a day and I'm back to square one.
Another interesting note...I just restarted the printer and attempted to install some as a test.  Now I'm getting a new error:

"Windows cannot connect to the printer"
Operation failed with 0x00000574
So, if you go into the "Print Management Console" on the server, do the printers show OK there?

And did you use the "Network Printer Add Wizard" to create the shared printers?

Wayne
The printers show up normally in the print management console.  I actually used the console to migrate most of the printers from an older print server though some I added using the Add Printer dialog.  I get the same problem on all printers on this server.  I was able to install them yesterday but now on each machine I try it on I'm getting denied access, even as the domain admin.  On machines logged in with a regular AD account it prompts me for a name and password and fails with the same error regardless of what ID I use.  I verified permissions on the individual printers and the Everyone group has print rights.
Ok, please ignore the addition 0x00000547 problem, that was because of a bad DNS entry.
Then something has happened from yesterday. Did you try to restart Print spooler service on  printer server? Did you try to restart server?
ASKER CERTIFIED SOLUTION
Avatar of First Last
First Last
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Found my own solution