> However, since you're using a network attached printer, why > not just have RSCS print directly to it, instead of routing > the print through the Linux guest? RSCS has very robust print > queue management, imho, and this will save you cycles on the > host. It's easy to configure RSCS for network attached > printers, see the RSCS doc for details and examples.
Not uncommon situation: the LPD implementation in the printer gets confused if multiple jobs come in at the same time from different sources (remember, there's no disk space to spool jobs, and memory is extremely limited on most embedded print servers). This causes jobs to be lost or corrupted. Also, if you have multiple protocols enabled (eg, SMB and LPD), the embedded print servers tend to lose output. HP JetDirect cards are particularly bad about this. Funneling the jobs through one source (especially one that can spool and queue jobs) is generally a good idea. Another thing that you should check: did you set the NJE nodeid of your VM system in SYSTEM NETID when you saved CMS? You'll have weird unexplainable problems with LPR links very similar to what you're seeing if you didn't. -- db
