If you have not already resolved this issue, we suggest you search our online knowledgebase for this product: Phaser 6180.
Alternatively, you can visit our Contact Us page for other support options.
My client has a Xerox Phaser 6180DN on their business Domain. One day it got a 166-324 error and went offline. After troubleshooting and looking over every other ticket on here we still are unable to find a solution.
The Xerox printer has a IP Address os 10.10.1.36. Everything is set correctly on the printers network settings. It is shared on their Printer Server in a Windows Server 2014 envionment. Before I power it up from the server I opened a CMD window and set a continual ping to 10.10.1.36 -t. As soon as I power it up within 15 seconds I start to receive successful replies from the IP and everything looks good. Around 15 seconds later the 166-324 error shows up and immediately at the same time I can see the printer go offline in the CMD window. I've been able to repeat this issue over half a dozen times. I've read on here that it could be a corrupt print job stuck in the queue so from the Print server I stopped the Print Spooler... then went to %windir%\System32\spool\PRINTERS and then deleted everything in there and restarted the Print Spooler. The same issue with it going offline happened exactly as before.
I was even able to log on to the printer interface for a short amount of time right after it booted up and everything looks fine. As soon as that error comes up it goes offline and the only thing that brings it back up for a short time being is rebooting the printer.
Any thought or help would be greatly appreciated.