Printer error message waiting

[n25an]

Does anyone have any idea what is actually going on when this message is displayed...

Situation: Km 4035 prints only after customer power cycles the machine.

Hardware: Rx 30 server for pharmacy work and windows lan network... (routers, switches, no windows server)

tech evaluation:

Tech checks km 4035... Km 4035 says its in a wait state...

Tech clears copier disconnects from network... Runs a 906 and reinstalls firmware...

Tech runs crossover cable to km 4035 and prints...
Tech connects km 4035 to network and prints...
Customer sends print job from rx 30 to km 4035... Km 4035 goes into wait state...

Tech contacts rx 30 tech support... Rx 30 tech support has problems printing to km 4035... Job is processed on print que but no print job just wait state...

Rx 30 tried using a printer connected via a parallel cable to the rx 30 server... Unable to print, then if it prints not the required amount of copies and then eventually it settles on wait state after 10 jobs...

At this point a 3 hour backlog of print jobs start pouring out of the km 4035...

Tech concludes something is wrong with the network... Network was hit by four power outages the day before...

Techs, copier and rx 30 techs, conclude... Something is fried on the network... Either a router or a modem...

Proffessional network technician will be arriving onsite tomorrow...

My question... What does the error message waiting mean in relation to a print job... And what could cause it...?

[Hemlock]

First thing that comes to mind is to turn off bi-directional support within the driver, so that jobs are printed once spooled as opposed to requiring any interaction after the fact. But I haven't had coffee yet and could very well be wrong.

[HenryT2]

Did you check the driver and the emulation on the printer itself ? Also, ( have seen this on some other models ) , check the RAM disk ,you may need to add some ram to that unit .

Good Luck . Please keep us informed on the progress, and the solution .

[blackcat4866]

I'm guessing that this app is not using a standard KX driver, but sending a PostScript or PCL coded print job directly to the IP address.

I happen to agree with the network diagnosis. My guess is the router. Maybe try a different port? =^..^=

[D_L_P]

Printing via crossover worked which 99% of the time eliminates the machine. If your network is lagging badly that will cause some serious issues with spooling print jobs. Power surge killing just one router will overload the network traffic on the rest.

But from what you describe, I'd say the Rx30 is the problem. And having issues with parallel printing makes even a stronger case that the Rx30 system is overloaded. I'd disconnect the Rx30 from the network, reboot and let it recover to an idle state. Then flush out all the print jobs on the parallel printer, then connect to back to the network.

[n25an]

Customer brought in their it person and he fixed the issue...

[n25an]

one of the linksys routers got fried...