6180 MFP-D Lion 10.7.4 consistent broken pipe and postscript errors only over network connection

[Kimzi]

SNMP can be turned on by default in the PPD, it's just a work around.

And yes, it does interact with CUPS. Thats why the command is like this in the PPD:

cupsSNMPSupplies

If LPD works, you dont need to turn it off, just if nothing else seem to work this can be tried.

You said the fault did come up only when connected through the network, thats why I brought SNMP up. :)

You can also turn it off in the PPD.

Thanks!

[cursulak]

Hello,

I have tried the LPD and IPP queues with and without the PPD file. LPD does work, IPP does not (not supported I believe) When using the PPD file it's the same error, when using generic postscript the printer refuses the job at the printer level. 

I am unclear why turning off SNMP will make a difference. it's a monitoring protocol and generally does not interac with CUPS unless setup to do so. I am not setup to do so. My errors are coming from the CUPS engine.

The xerox installer does not install a printing scout as per your desciption. 

[Kimzi]

Hey, cursulak!

If the above suggestion does not work, try using the LPD queue LP.

You can also try to disable SNMP because the problem only occurs on networked devices it is probably a network issue.

Disabling SNMP means you wont get these messages and will probably be able to print without any further problems.

SNMP is disabled on the mac by doing as following.

Open the Terminal.app.
Can be located in “Applications” -> “Utilities” -> “Terminal”

Write as following:
Snmpconf –g basic_setup

Choose the “snmpd.conf” file, if you have two of these files, select the one named “etc/snmp/snmpd.conf”.

Write as following:

No <ENTER>
Yes <ENTER>
No <ENTER>
No <ENTER>
No <ENTER>
No <ENTER>
No <ENTER>
No <ENTER>

If you get a message saying the file already exists, write this command:

Overwrite <ENTER>

Restart your MAC and SNMP should now be deactivated.

 

You may also need to remove the Printing Scout by doing as following:

This program is included in the driver package.
Start the “Finder” and go to Applications -> Xerox -> Printing Scout.

Take the whole catalogue and slide it over to the Trash bin, right click and select “Empty Trash”. After this you will need to restart your MAC.

Thanks!

[RuiKZ6N6K-xrx]

You also can try other thing. You need to take out the driver from the equation. On the printer protocol window, where is the "use" field, chose "other" and point to the PPD from that printer. Regards Rui

[cursulak]

Yes I had read a similar posting on HP printers and tried that on 3 of the machines, one being the base install. Didn't change anything, slightly different postscript error, but essentially the same. no output and broken pipe. 

I am interested to see if it works on a 10.7 original release, I am going to try that over the weekend. If it does, then I know the issue is in the 10.7.3 or .4 update. That is the only thing I haven't tried yet. 

[RuiKZ6N6K-xrx]

Hi, When installing the printer, please chose IP and not Default. In the IP settings select LPD, then set the ip and in the queue enter "ps". At "Use" select the driver that you used before. Hope it helps Rui

[cursulak]

I have 10.7.4 install on an all Mac environment with 8 machines. I did download the 10.7 dirvers and have installed them on 5 of the 8 machines. Our printer is a 6180_MFP-D. 

I get broken pipe messages, and postscript errors on every single machine except one, the machine that is connected via USB (server). In order for me to acutually use this printer across the network, I have to share it through the host. All 4 other machines trying to print via Bonjour printing cannot with the above broken pipe and postscript errors. 

I suspect this driver is not fully 19.7.4 compatible to have such consistent failure across network connections. I have put hte USB connect to each of the 5 machines and it works fine through USB. I suspect the network component of this driver be tested some more. 

I did test a brand new MacBook Pro with a clean, base intall of 10.7 on it and had the same issue. This leads me to believe my previous comment. 

Hopeing a patch to this is released soon.