LAN Attached printer losing connection

I'm having an issue with this printer every Monday morning - this is our most heavily used printer; prints orders all day long. It's an HP M507. Was an M402 previously, but had these same issues with the old one too.

Here's the issue: On Monday mornings, It will start printing and then stop with a CPA403D Operator Action required - C or R - when the output tray is full. Which is normal.

Cancel or Retry are the only options - But you can reply with an R as much as you like, you keep getting the same message. Or sometimes the writer will end itself after responding with an R. Every other time you're forced to answer with a C eventually.

Either way, you're restarting the writer, which then causes the spool to restart printing at page 1.

There's been a couple of times it's just started printing junk after the restart and has to be ended/restarted again. Then it will print fine again.

Local LAN attached, but the i is hosted remotely and connected to our local network with VPN.

Again this only occurs on Monday mornings; it behaves fine the rest of the week. Every Sunday afternoon, the system goes into restricted state for BRMS backups.

Monday mornings are the heaviest days so the output bin is almost guaranteed to get full on the first print of the day.

Spools are being transformed by TLA Forms by TL Ashford, which takes some processing time since the i is remote, so I've schedule the print for about an hour before the user is scheduled to arrive.

I at first thought that I was printing the spool before the system went into restricted state as I had some extra jobs scheduled for printing over the weekend, so it would make sense it would restart the spool over at page 1. But I have since changed the schedule so that's not it.

I also found the IP time-out setting on the printer itself and upped it from 5 minutes to 30 minutes - no effect.

Nothing has worked so far. It's strange that the printer will print fine until the output bin is full, but then not respond properly to the Op Action required message response. We end up wasting a lot of paper because of the duplicates.

Anyone have any other ideas I could try?

Thanks

Bob Cagle
IT Manager
Lynk