Wont power up when network cable is connected

[Joe Arseneau]

Unless you already know how to fix and diagnose printer internals, you are left with returning it or paying somebody to fix it.

[BenBrig]

than what do i do if its a hardware issue. This thing is New.

[Joe Arseneau]

It absolutely has to be a hardware issue with this machine, it can't be settings, every single setting has been thoroughly wiped out and it still has issues, and it has kept those issues in multiple firmware levels, even across completely different generations.

[BenBrig]

turned unit on and now it prints from my computer through the network. only problem now is my touch screen on the printer does not work. it is on and beeps when i touch it but nothing happens. cant log in cant access any settings or nothing. the screen and settings all work when i have no network cable connected.

[BenBrig]

Upgraded printer to newest firmware. Via Altboot. Upgrade sucessful.  When network cable is connect the printer still freezes. What can be wrong. This printer is new with only 50+ prints.

[Joe Arseneau]

Latest firmware

[BenBrig]

signed in as admin and reset to defaults. plugged it into my network and now it works. problem now is my screen on the printer is froze. how do I update this printer? maybe thats what it needs.

[BenBrig]

That is not my serial number. My serial number is C7X225080

[Joe Arseneau]

Looks like they may have been less than truthful.

Due to the fact your config sheet says it was last updated in 2014, I decided to go digging on your Serial number (New machine would never have been updated, let alone 3 years ago.

This machine was well used (Minimum 49768 impressions) by the previous owner, and Xerox has records going way back, meaning it was under contract and metered supplies.

Best bet is to wipe the device via altboot and use the latest firmware to do so. (Every setting will be lost)

Other option (workaround really) is to just disable everything at the copier, plug it into the LAN, and enable 1 by 1 until you find what one kills it (SNMP or WSD would be my suspects). But even when you find the culprit, finding the source would be a real pain. Could also be a secure certificate that fails due to the IP not being correct for it.

Check your PM's.

[BenBrig]

it only has 52 prints on it and thats from me printing test pages and copy's.