mp4001 sometimes offline (ping ok)

[Mark Bbb]

Indeed, the controller of a mp4001 was sometimes ok, and sometimes not ok.
It kept getting worse in time...
So it starts failing once a week and gradully became worse to 3 times a day, going offline.
When user toolls are accessed when the mp4000 was offline, only the "counter" is shown solid black, all the rest is gray.
So, from that point we knew it was the controller.
So, an electronic board can work sometimes good, and sometimes bad.
That is not good news; it makes trouibleshooting far more difficult!

[MIGUELMARCHENA]

I happened something similar on two occasions

the first was a salesman who arrived and his cell phone took the same ip from the machine.

problem two a virus in an accounting program.

[Mark Bbb]

I happened something similar on two occasions

the first was a salesman who arrived and his cell phone took the same ip from the machine.

problem two a virus in an accounting program.

ok

[CopyBats]

Does it show as offline on multiple computers? Are you able to access the machine from WIM?

I have found 2 usual causes for this problem

1) IP conflict ( another device on same network has same ip)
2) Customer has selected the pause printing option unknowingly on the machine. When you go to see whats printing on the printer, you'll have the option to pause the printer and bring it back online ( this may only work if there is only one computer there)

Good Luck

[Mark Bbb]

Does it show as offline on multiple computers? Are you able to access the machine from WIM?

I have found 2 usual causes for this problem

1) IP conflict ( another device on same network has same ip)
2) Customer has selected the pause printing option unknowingly on the machine. When you go to see whats printing on the printer, you'll have the option to pause the printer and bring it back online ( this may only work if there is only one computer there)

Good Luck

contact to WIM was impossible at the time of being ofline...

[tonerhead]

This may be a wildcard shot, but we have an overbearing IT dept, anytime someone spooks them with a possible security issue, they implement a response without thinking through the consequences. They received notice that SNMP is a GREAT security issue so what do they do but turn off snmp throughout all of company. Got a lot of issues like you were describing. Of course the correct way to do it is to replace the read/write filters with something other than Public in SNMP. Guess they didn't read that in the security warnings. The first morning they pulled the trigger I had 20 printers show offline before 8:30. And did they tell me what they did? H3LL NO!! Had to figure it out on my own because snmp was their dirty little secret.