Link to home
Start Free TrialLog in
Avatar of RyanHenry
RyanHenryFlag for United States of America

asked on

HP Network Printer

All,

I bought a new HP Laser Jet M401dne printer to replace our old network printer.  For some strange reason after I put it on the network and then shared it from my print servers, it won't let me add it to peoples Pc's correctly from the network.

For example with my other printers you could just UNC to the print server, double click the printer you wanted, bam you had it.  Or you could go through Windows 7 add printer wizard and select the printer you wanted from ADUC.

If I try either of those ways now, it will contact the printer and eventually tell me either access is denied or it won't install correctly.  In both instances after adding the new printer to a Pc, it will show up, but it will have the yellow troubleshooting mark on it and won't be available.

The only way I found around this is to add the printer via connecting to the tcp/ip port and then sticking the driver cd in, selecting "have disk" and then the printer installs perfectly fine.

I am not sure why I can't get this to work via the network?  I have checked all of the permissions but can't see whats missing compared to the others.  I installed an HP color printer a few months ago and had it up and working in minutes.

Would greatly appreciate some help on this! thx...

Screen shots of errors below.
printer-error-add-printer.PNG
printer-error-add-printer-2.PNG
printer-error-add-printer-3.PNG
UNC-printer-error.PNG
Avatar of Michael Machie
Michael Machie
Flag of United States of America image

Excellent job explaining your problem.
 Is it a 32 or 64 bit driver and is the server/pc where you have installed it a 32 or 64 bit O/S?

You can install the driver onto a 64 bit server or pc and share it, but 32 bit clients connecting to it will not be able to either access, or install, the driver. You can UNC path, see it in ADUC and select it, but you won't actually install the proper version.
If this may possibly be your issue, then you can try adding the 32bit version of the driver, from HPs website, onto the 64 bit server/pc from the 64bit print driver - it is a tab within the driver properties that says 'add additional drivers'. Once the 32bit is installed, you can pull down to 32 bit clients, usually.

The reason you may need to use the disk is because the driver you are pulling from the server is not the proper version so installing on the client pcs locally is the only option that works. When installing from the CD it will install the proper version without prompting the User, so you may not have noticed.

You can start there if you'd like.
Avatar of RyanHenry

ASKER

Thanks for the comment!  I am back at work today and wanted to follow up.

I did already select that option for both x32 and x64 clients.  I will go to the HP website and try downloading the latest drivers though and see if that fixes the issue.  the ones that are on the server are from 2012.

I'll let you know soon!
Very strange.  So the drivers from the HP site didn't work, but the driver from my Color printer which is a HP LJ M541 worked on one of the servers.

So my backup print server which is also a DC, is working fine now with this color driver!  However my main DC which exactly mimics the backup still wont allow me to connect even with this color driver.

Very strange indeed!
Very strange. You may want to delete and rebuild the printer on the problem server, then try to connect again. I say this because I actually had the exact scenario this morning where my Users could connect to a printer fine, been using it for 3 years, and now today they could not print or connect - 'access denied' message. I rebuilt the driver with the exact same share name and re-started the Print Spooler service to resolve.. didn't even need to pull the new driver down since the share name was exactly the same.
ahh... Great idea!  I'll be out until Monday and I will update you then!

Thanks for the help, really appreciate it!
So it's def driver related.  I tried to delete the printer and re-add it but it keeps using the older drivers.  problem is, I can't find out where the drivers that its using correctly on DC02 are located?  If I could just find those, I could then add them to DC01 when I re-create the printer.

Its the smallest thing, but look at the screen shots, you'll notice that one driver is from 2012 and the other is 2013.  The 2013 version works, however I can't for the life of me find where that's stored at so i can copy it to the other server.
Dc01-Non-Working-Driver.PNG
Dc02-Working-Driver.PNG
ASKER CERTIFIED SOLUTION
Avatar of Michael Machie
Michael Machie
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
Thx for all the help!  This worked like a charm!
You are very welcome. Please come back to EE again in the future.