I am starting to think your printer setup is not the issue.
Can you try printing a test to ARCH again and after it fails do a /nsu53 or /osu53; lets ensure someone didn't work with your security team and they put something in place to only allow a certain method to archive.
Another issue I have run into, some transactions (me22n or va01) will ignore a user's default output device. When we first setup a archive process for our POs the functional team's consultant started blaming me for a mis-configured printer setup; turns out what was setup was set to archive only and my co-workers also needed the PO to print. Reviewing tx SP01 I see no spool entry, the archive process actually steals the spool. After some review they found that the process had 3 options (Print, Archive, Print & Archive) and they fixed their configuration.
Long story short, who is in charge of the master configuration data in that system for this check run process?