Xerox Phaser 6280 116-324 Controller Error

[Long Lane]

Thanks. AFAIK, there is only one Windows machine on the network running as a virtual machine. I shut it down in order to isolate the problem and it continued. Next to a number of Macs, we also use a number of Raspberry Pis as non-speed critical devices/servers.

Many thanks for your help. I was about to give up on this Xerox printer and switch to HP. I will remain loyal and continue purchasing Xerox cartridges!

LL

[Joe Arseneau · Accepted solution]

WSD is what Windows 8-10 use by default.

So if someone had the printer installed, and updated to Windows 10, it will have converted any port it sees fit (most) to WSD, and likely replaced the Xerox driver with a MS Class driver, which could be the cause of your issues.

Likely somebody recently brought in a PC that was updated to Windows 10 Anniversary (Version 1607)

If you can find them, delete any and all Xerox drivers from it.

Install and choose The printer I want wasn't listed (If it is there and you pick it, you will get a WSD port)

Then pick this option or they will just redo your port on next reboot or Windows update that updates it's class drivers

[Long Lane]

Indeed, had the same idea. See my previous post: WSD is the culprit!

[Joe Arseneau · Accepted solution]

So is it just the network or a subset of your network?

Hook it up to a switch on it's own,wait, add a PC, wait, add a Mac, wait, Send a job, wait. Find out what makes it die in other words.

You could, if you have a crossover cable, just wire into it direct and see if it fails without a switch.

Log files can typically be opened easily, but not easily read (Grab an Application like 7zip and it should open the file) but I'm pretty sure there are none on the 6280

Have you tried simply killing all ports in the left column and then enabling them one by one in 30 second intervals? No way for something to hide that way, then you would know the port in question and could capture the file via Wireshark. (Properties > General > Port Enabling)

You can also change the Hostname to stop anything actively seeking that over the IP (Properties > Protocols > TCP/IP

[Long Lane]

Here is another test I did:

• I disabled all the protocols (LPR, Port9100, IPP, SMB TCP, SMB NetBEUI, FTP, WSD, SNMP, CentreWare, mDNS, Telnet)
• Then I enabled them one by one. 
• The error occured as soon as I had WSD enabled. 

I did some research about WSD but am not sure, I do need it.

Is there a specific port which is open for WSD? What could make the printer fail based on the WSD protocol? As far as I remember, the 6280 is not Airprint compatible. 

Thanks

LL

[Long Lane]

Hi Joe,

Thanks for the quick reply. Without any further doing, the printer simply displays the 116-324 Error and asks for a reboot (takes about 15 sec between connecting to the network and crash). No printer job is active. 

I disabled IPP and mDNS but unfortunately, it still crashes. So that rules out bonjour.

Very odd.

Is there a way to examine log files?

Thanks

LL

PS: why I thought it might be bonjour related is, that the Error continued when I switched from one subnet to another (on the same physical network). 

[Joe Arseneau]

I'm fairly sure it won't be Bonjour that is at issue, but that is easy enough to diagnose.

Remove the printer and simply re-add it as an IP printer (IP tab) and choose either LPD or HP Jet Direct as the protocol

Put in the printers IP

Queue name for LPD will be lp (Lower Case LP)

Change the name to the printers name

Choose Select printer Software from the Use dropdown

Type 6280 and pick it from the list.

Click Add

While there is no driver for 10.12, the 10.11 installs without error.

If it still fails, retry, but instead of using the 6280, try the Generic PS ppd and see if it gets different results (At that point you have eliminated the driver/PPD, Ip address and the Mac)

So now we keep moving, lets pretend the problem job is not still on the Mac, it is on the LAN, and it is just waiting for the printer to be on the LAN, and as soon as it shows up by Bonjour, the printer crashes (Bonjour goes by name, so the IP address does not in any way affect this)

So we disable the ports printer side:

Admin Menu > Network Setup > Protocol

Disable IPP and Bonjour

At this point I believe I have covered everything that can be. I work in a Xerox test environment, we have a 6280 on another floor and I successfully printed using the driver I screenshotted to it, and it stayed online so it is not killed by anything 10.12 related (10.12.2 at tested time)

I honestly can't think of another thing to try, so give me the results of my things I listed and I will dig more if needed.

[Long Lane]

Here is the situation: I use my Phaser 6280dn for printing high-quality glossy documents and am very happy with the results (that's in 2017 for a printer which was launched in 2008). Printing glossy documents doesn't happen every day, so the printer is turned off when not in use. For regular printing, we use a HP b/w laser. I believe, that the last time the Phaser was turned on might have been before I upgraded to macOS Sierra. 

So I needed to print out something today and turned it on and almost immediately got a Controller Error 116-324 with the suggestion to restart the printer. Restarting the printer does not clear the error. It comes back as soon as it has restarted.

I went through the forums and also had a brief conversation with the firendly Xerox Support but haven't been able to resolve the situation. (I managed to print out my print job using a USB connection though.) Here is what I did/tested for:

• Reset the printing system on all connected Macs (this clears any pending print jobs, etc and requires the user to re-install printers)
• I installed 3.2 of the printer drivers (had 3.1 before) 3.2 approved up to 10.11
• Rebooted some network switches
• Changed the IP address of the Phaser
• Changed the subnet of the Phaser
• Unplugged the network cable, turned the Phaser on - no problems. Plugged the network cable in - Error. 
• Same as before routing through a different switch, but takes longer before the error appears for the first time. Faster when using the same route.

I am wondering if there is something wrong with the bonjour protocol implemented in macOS Sierra and the Phaser doesn't like it. And as soon as a Sierra machine is on the net, it will kill the printer? 

I am very grateful for suggestions on how to resolve this.

Would be a shame not to be able to continue using this printer (although I might be able to put an old Mac mini in front of it, connect via USB and then share the printer on the network - might be workable, but certainly not desired).

Thanks

LL