Client Acess printer session rebooting PC

["Lou Schmaus" <lschmaus@xxxxxxxxxxx>]

I have an interesting but serious problem at one of our clients sites.

 

They are rolling out access to the AS/400 at their retail stores, and one of the functions is printing price tickets from Monarch printers. We tested the hardware thoroughly at the office on our local Lan, and everything worked fine. Now we are having problems when installing the hardware at the stores.

 

The PC's are running Win2000, and connected via DSL lines. The Monarch printers are configured with Client Access Express V4R4 and latest service pack. The Client Access settings are set for Host Print Transform, 'Other Printer', and using the latest Monarch 9840 driver downloaded last week.

 

The problem is that on two of the five PC's reboot 9 out of 10 times as soon as a spool file is created and sent to the printer session on the remote PC. It doesn't seem to be the printer itself, as we get the same behavior if the printer is turned off, and just the C/A session is running. We have tested the hell out of the remote location, checked the power output on the wall outlet and surge supressor with a meter, swapped cables, keyboards, etc... As soon as we release the spool file, and the lights flash on the DSL router, the PC goes does a warm boot, just as if magic fingers had done an ALT-CTL-DEL. But not EVERY time, just 9 out of 10 times.

 

The problem appears to be confined to particular PC's. With identically configured PC's at the same location, one PC will reboot, and the other will work fine. The PC's are brand-new, right out of the box, with identical hardware configs. I cannot change the hardware or software config, as they are mandated by the software vendor.

 

I am absolutely stumped. We installed the software and tested each PC, with associated printer, connected to the local Lan. PC's were run for days without being shut down. There were NO problems. Only thing that is different that I can see is now they are remote, and the network settings were changed on the PC to connect via DSL line. We have 7 more of these PC's to config and deploy, and I don't want to be driving all over Brooklyn and Queens in the holiday traffic trying to fix this at remote locations.

 

Any ideas?

 

 

TIA,

 

Lou Schmaus

CCA, Inc.

Jackson, NJ 08527

lschmaus@link400.com