Solved

Print drivers not loading on client machine

Posted on 2014-11-19
9
273 Views
Last Modified: 2014-11-20
I have a print server set-up with multiple printers.
All my Xerox printers when pushed out via group policy work fine on my Windows 7 machines.
All my other printers when pushed out via group policy do not allow me to print.
There is no error. The print job simply does not show up.
It is not until I browse to the printer UNC path on the end user machine, right-click and choose connect does the print driver load and then I can print to the printer.

On the print server, all printers that do not allow me to print to them from the Windows 7 end user machines have the Additional Drivers on the Sharing Tab greyed out.

What do I have to do so all printers can be print from?
0
Comment
Question by:Robert Mohr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
9 Comments
 
LVL 5

Accepted Solution

by:
Aaron earned 500 total points
ID: 40453701
Make sure that the drivers match the computers or provide a 32 bit and 64 bit version driver and do them individually. Somthing that often gets overlooked is the OS version but it can be a pain when it comes to printer drivers. Also make sure the client PCs have permissions to those printers. If they all have rights to the printers and all that then the next place to look would be at what other printers you have. I am guessing that they are using a static IP and not a host name? That might come into play with some brands of printers. If this doesn't work I can think of a few more ideas but I am pretty sure it is either permissions or drivers that are the issue. Good luck!
0
 

Author Comment

by:Robert Mohr
ID: 40453733
Thanks Aaron. They are all IP based so no issue there.
I will delete and re-add then test one of the printers in question and make sure it work with my W7 clients.
0
 
LVL 5

Expert Comment

by:Aaron
ID: 40455048
If they are IP based you can try to access the printer website with a browser from those machines. Is it possible that you have other dynamic IP machines that try to take and lease the printer IPs or are the printer IPs static and DHCP disabled? I just figured that is one test more you can do past the ping test to make sure you are pinging the printers.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:Robert Mohr
ID: 40455101
Aaron -

Excellent questions.
The printers have statically assigned IPs.
I half think it is related to the drivers somehow. They are older HP devices and could be "flaky" on a Windows 2012 R2 print server.
Testing now actually and report back.
0
 

Author Comment

by:Robert Mohr
ID: 40455214
Just tested the following using a test machine with a user that has domain admin rights.

1.

Uninstall Dell 1320c driver (type 4) that was automatically installed from Windows when setting up print driver on print server. Note this install method never gave the option to install a 64-bit then 32-bit driver.

2.

Re-install Dell 1320C driver (type 3) manually from drivers that were downloaded from manufacturer and was able to install both the 64-bit and 32-bit versions.
When deploying printer again using the type 3 manual install and printing from test machine, the client machine asked to install driver at first use twice and then gave "A StartDocPrinter call was not issued" pop-up. Chose OK, tested print again and it passed thru.

Next test is on the HP machines. These might be trickier given that they are older. Will report back and hopefully finish this!
0
 

Author Comment

by:Robert Mohr
ID: 40455238
As I move thru these HP printers, what is preferred for print drivers?
PostScript
PCL5
PCL6
0
 

Author Comment

by:Robert Mohr
ID: 40455377
Aaron -

It worked. I relied too much on the automatic Windows process and chose the driver that is said matched the model of printer. It seems that when I pull down the driver from the manufacturers website and deploy via group policy with that printer, it works.

I have about a dozen or so printers to do this with but am satisfied with my test on the two printers from Dell and HP.

Thanks again!
0
 
LVL 5

Expert Comment

by:Aaron
ID: 40455389
That's great, for the record I usually go with Post Script or PCL 6. If performance is an issue usually use the PLC because PS can sometimes slow things down. However I think that PS does give a bit more options for the user. Either one should be fine for what you described. Glad I could be of help!
0
 

Author Closing Comment

by:Robert Mohr
ID: 40455390
Downloading the print drivers directly from the manufacturers website and then choosing those drivers during installation of the printers on the Windows 2012 R2 print server seemed to work when deployed via Group Policy.

The no-print issue seemed to occur when I used printers that Windows had already loaded and available to use during printer set-up.

Not sure why the Windows process did not work but choosing the driver from the manufactures website did.
0

Featured Post

Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Static IP Address Assignment 10 77
Best print server for Mac + PC Environment 1 35
Replication in Hyper-V 8 37
Promote Server 2012 R2 on Server 2003 domain 13 17
OfficeMate Freezes on login or does not load after login credentials are input.
Are client relationship the only driver of a successful MSP? While important, client relationships are only one component. Learn how else MSPs can broaden their horizon and differentiate themselves.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question