Printing Problems windows 7 x64 with Server 2012R2 Print Server

[jonnykewell1]

Ok guys I have an odd one here. I've just set up a new domain controller at my primary school with server 2012r2. This server is also the print server and only has 1 photocopier installed a Konica Minolta c452 Bizhub. I'm using the PCL C652 series driver as this covers multiple models. I'm pushing out the photocopier with a script which is one we use at my secondary school and I know this works fine. My windows 7 64bit laptops just won't connect, download the driver and install when connecting to the server.

 

If I choose add printer browse the network and try connect to the photocopier it just sits at connecting to printer then fails with "cannot connect to printer" error code 0x0000000a

 

If I choose to add by local port, enter the IP address of the copier, then browse for the 64bit driver from the servers desktop, it installs and then prints with no problems. There are only two drivers assigned to the printer, both the same version but one 64bit and the additional 32bit driver.

 

Firewall is switched off on both client and server just to test if something was getting blocked, I've stopped the spooler, cleared the drivers from c:\windows\system32\spool\drivers but still nothing. Has anyone got any ideas what could be stopping this connecting through the server? It sounds like it can't decide which driver to pick.

 

Thanks.

[Duke5A]

This might have something to do with Point and Print Restrictions. On the system that you added the printer on locally, delete the printer and try adding it again off of the print server. The difference being this time since you added it locally the driver will already be installed (deleting printers doesn't remove the driver). If it adds the printer successfully then you need to disable Point and Print Restrictions in policy.

 

Computer Settings > Administrative Templates > Printers > Point and Print Restricts - Disabled

[synaesthesia]

With any modern client/server setup like yours I would strongly suggest ditching the scripts and sharing them with GPP. Far more consistent and reliable than a script ever will be.

[Duke5A]

With any modern client/server setup like yours I would strongly suggest ditching the scripts and sharing them with GPP. Far more consistent and reliable than a script ever will be.

 

Not from where I'm standing; GPP is the most inconsistent and temperamental thing I've ever had the pleasure of working with when deploying printers. I fell back to my VB script and haven't been happier. Even on wireless devices that gang up on a single access point the login script always pulls through.

[timbo343]

Ditto about the vb script, GP didnt do anything for me however my script lets me map printers based on computer name, AD Group and username. Been working flawlessly for 3 years now.

 

Strange about the driver. We have the same model konica but without thd issue you have. Try removing the driver and only install the 64bit driver, see what that does.

[psydii]

There are hotfixes that make gpp reliable and consistent.

 

Here's the latest one.

 

http://support2.microsoft.com/kb/2912760

 

(Hotfixes to individual files are cumulative, so this one (should) continue to resolve all previously patched bugs)

 

Make sure you've also got the printers updates:

http://support.microsoft.com/kb/2647753

and

http://support.microsoft.com/kb/2896881

 

and finally (or firstly) the enterprise hotfix rollup and its related updates:

 

http://support2.microsoft.com/kb/2775511

Edited October 4, 2014 by psydii