Network Packets restarting machine? or bad switch?

[DallasTech]

I have a weird issue with a customer's network.

Muratec 2850, works fine, until plugged into network, then freezes every minute or so and restarts

Muratec 1430, works fine, until plugged into network, then restarts every minute

Muratec 2830, works fine, until plugged into network, then restarts every minute.

All machines have been tested (network print and scan) at the shop and work flawlessly with no problems. I have tried different IP addresses, network cables, ports on the switch, etc.

I am starting to think it's a switch or maybe a computer sending out a broadcast that is restarting the machines? anyone got any ideas?

[Vulkor]

Bring your own Router to the site, plug in two cat 5, make your own mini network. Make sure IP of router is same range as Copier.

Ping it continuously. Print, Scan etc.

Savin had a firmware update for issues similar to this. Is Customer using High End Linksys or Cisco? Link Flapping has been causing issues.

[Eric1968]

I think the machines are receiving invalid data. Had this a few times with Oki printers. These printers gave fatal errors and then had to be rebooted.

I would say this is a problem for the customer's IT department.

[Guest]

I had a similar issue a long time ago that was caused by a print job originating from one of the clients that got stuck and started sending corrupt data to the printer. I looked at the print queues on each client machine until I found one that had a job with a print error and about 20 jobs stacked behind it. (The original print job didn't print, so the user just kept trying to send the same job over and over). I had to delete all the jobs in the queue and then delete and re-install the print driver (just to be safe).

Good luck...

[Vulkor]

I've seen prints lock up a machine. But to reboot. Does the copier keep a log?

[Wynard]

Just a quick hint: If a print job refuses to have itself deleted (which is often the case with corrupted print jobs), stop the spool service and navigate to C:\WINDOWS\system32\spool\PRINTERS and delete everything inside, but not the folder itself... which will emtpy any print queue. Hope this helps

EDIT: An a bit more torough explanation

[Vulkor]

Thanks Wynard! I've had to restart the Spooler service before due to print drivers not being able to install because someone tried deleting a printer while it had a job in que. It of course fails to delete and has Deleting in its comments. Sometimes only way is to restart Spooler service since it won't cancel the job either. THANKS