cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Member
New Member

Unable to connect to shared WorkCentre 7335 on Windows 2012

Hi,

 

We are in the process of migrating from W2K3 to W12 for our printing services and I'm having an issue getting the Xerox WorkCentre 7335 printing to work.

 

I've installed version 6.20.19.0 of the driver fine on the server, shared it out and can test print OK from here. However, when I attempt to add the printer to my W7 workstation, it fails when adding the driver with a generic 'cannot connect to printer' message. I've set up Kyocera and HP's the same way with no issues.

 

Can anybody shed any light on what might be causing this? Is there extra configuration needed to get this to work?

 

Any help appreciated!

 

Simon.

0 Kudos
2 Replies
Highlighted
Community Manager
Community Manager

Re: Unable to connect to shared WorkCentre 7335 on Windows 2012

Hi jacksos,

Thank you for using the Support Forum. Please take a look at this solution for adding a shared printer and see if this will help.  If not please consider contacting your support centre for further assistance.

Thanks,
CherylO-Xerox
Community Manager

Be sure to click Kudos for those who have helped you.
Select Accept as Solution for posts that have helped to solve your issue(s)!

0 Kudos
Highlighted
New Member
New Member

Re: Unable to connect to shared WorkCentre 7335 on Windows 2012

Hi Jacksos:

 

Did you ever find a solution to your error?  We're in the same situation here with our 7435.  

 

Additional Details:

The intigrated Windows 2012 v4 drivers work for both 64bit and 32bit clients, but lack the additional options like sucure print.

 

Installing the latest Xerox v4 PCL6 version 6.20.19.0, and Xerox Print Experience Pack version 6.20.27.0 adds the additional options, but 32bit clients are unable to connect.  The error displayed on the client is "Windows cannot connect to printer".   Details show "Operation failed with error 0x00004005".

 

The error code hints at a 32/64 bit driver mismatch.  However, the whole point of v4 drivers is to eliminate the 32/64 bit mess.  

 

The support link proveded above seems to be for Server 2003, and not at all relivent to Server 2012. 

 

Thanks,

 

0 Kudos