Printing triple of every job

[Joe Arseneau]

See if this seems similar, this has been sent to Engineering before and it was declined for a fix, it seems the same/similar:

Problem:

When printing from newer Mac OS's 10.7 and 10.8 a user will see additional print jobs appear in the Mac queue. This occurs when printing locally from a Mac

or when printing from a shared queue. (Example of a shared queue Windows 2008

server pointed via LPR://server ip/printershare)

Solution: Declined

Decline Rationale:

This decline explains what and why the print status jobs are sent.

It also explains why they be getting stuck when printing through a Windows server.

What and Why the jobs now appear:

Our engineers have investigated this problem and are declining this issue because the print driver is working to meet new Apple OS design requirements.

As part of ongoing security measures, Apple operating systems starting in 10.6 prevent any application that does not need network access to complete its "work" from having network access. This includes print drivers inside of  applications. All print drivers (Xerox and Competitors) are bound by the same rules and no longer have access to direct network communication. Xerox uses the "Printer Status job" as their way to meet this security requirement and still be able to gather the necessary device information. If the job is titled "Supply Levels" this job is created by the Mac OS and is required to capture Toner Levels. This also occurs because of the above description.

Why jobs may be stuck in a shared queue:

Xerox does not support the following configuration: an LPR connection between

a Windows print server and a Mac client.

The Xerox Mac OSX driver contains custom XBDS filters/commands which are used

to communicate directly with the device. When communicating from a Mac to a Windows server, via LPR/LPD, the printer status jobs can hang in the Mac OS print queue. This occurs because Windows server cannot resolve the communication being sent from the Mac client. The reason the Windows server cannot resolve the communication is because the information sent from the Mac is meant for a

printer and not a Windows OS.

Second Possible Reason for jobs being stuck in the Mac queue:

The Mac driver intends to send this print job to the device, however in this customer's case the Windows Server is between the client and device. Since the

Mac does not know it is not communicating with a printer it continues to send

the Printer Status job, via HTTP (port 80), waiting for a response back. The server does not know it is being asked to act like a "printer," and does nothing with the job, and eventually rendering the job stuck in the print queue until it

is manually deleted.

Workarounds to prevent the jobs from occurring:

A. Disable Bi-Directional Communication (To configure a preset with bi-di disabled please perform the following)

1. Open any application

2. Select File > Print > Xerox Features

3. Select Advanced > scroll down and select Bi-Directional Communication

4. Select Off then Ok

5. Select the Presets dropdown

6. Enter a new name for this preset, select All Printers and select Ok.

Refer to the following link to describe how to set a custom preset as the new

defaults

http://www.404techsupport.com/2012/08/setting-printing-defaults-in-mac-os-x-through-presets-and-cups...

B. Configure the printer on the Mac using SMB instead of using LPR. Please refer to the following information on how to configure a printer via SMB

¢This is only valid for shared print queues¦

Below is a link with steps on how to add the printer on the Mac.

http://reality-and-a-half.multiversum.com/how-to-smb-connection-url-mac-os-x-10-5-10-6-10-7-windows-...

-This link offers the correct URLs for 2k3 and 2K8 windows servers to Mac OSX

all the way back to 10.4.

C. Modify the driver PPD file and remove the following command cupsCommands:

"ReportLevels ReportStatus". Removing this command will also prevent any bi-di communication to occur between the device and driver.

The modified PPD can then be loaded onto the Mac clients

D. Create the print queue using Bonjour instead of using an IP address. This problem only occurs if the print queue was created manually using an IP

address and it does not occur if the printer is installed via Bonjour

E. If Port 80 or Port 443 is blocked please add an exception to the Mac OSX

proxy.

[adamico1]

Yes, Managed Print Services. 

Basically, we are using both. We have users that print from Mac laptops and desktops to the Xerox devices. The driver is locally installed on the computer and we print to the machine over the network (we don't have Mac management, so we have to install the printer manually to all of the Macs). As of late, it seems that this may only be isolated to the WorkCentre 7225.

And to my knowledge, the one application is that is web based for the user's has a Unix backend. These print jobs are sent from the Unix backend to a Windows server that hosts the printer drivers. This also seems that it is only associated with the WorkCentre 7225. 

We have not seen this happen on any of the our other WorkCentre, ColorQube, or Phaser models. 

Do you have any suggestions for this?

[Joe Arseneau]

Is Xerox MPS this? Managed Print Services

We have run into an issue with Unix printing. When printing from any Mac, we are getting triples of any job we send

Are you using Unix and or Mac? If you mean Mac (using CUPS) is the driver locally installed on the Mac? Server installed?

There are definate issues printing with a server installed driver with Macs, a very similar issue is when a Mac is connected to a shared printer on a Windows PC/Server, that does cause an issue of duplicate and triplicate prints.

[adamico1]

Just started using Xerox MPS at my place of work. We have run into an issue with Unix printing. When printing from any Mac, we are getting triples of any job we send. Test print jobs from the Mac print dialog, jobs from Office, anything. I believe it is only happening on our WorkCentre 7225's. We also have a Unix server that certain jobs are sent thru from an application of ours and that also prints triple of everything. Haven't been able to get an driver to work properly. Does anybody have any ideas?