Best Practices For Wireless Printers Follow
We have a client who is running Zebra QL320 WiFi printers in their warehouse. When they need to print a label, our application sends a file to Commander, which sends the label format to a Windows Share. This all works fine here as it has at other sites. We are using Bartender Automation V10.
The issue we have is that occasionally the job will become "stuck" in the queue. The print job message is "Error printing". We can't delete the print job and it prevents further printing to this printer until we manually restart the Print Spooler service. I have never seen this happen with a hard wired printer (we have used Zebra, Intermec and Datamax).
In more detail:
1. Printers are all configured on the WLAN and been given reserved DHCP addresses.
2. We have added multiple TCP/IP ports to Windows for each of the fixed printer IP addresses.
3. We have installed the printers as Windows printers, using the port above (e.g. PICKING_1 -> IP_192.168.0.30) and the Seagull Scientific Drivers v7.3.1
4. These printers are then shared.
5. Everything runs on one server (SQL Server, Bartender, Commander, Printer shares)
6. So we might send a job to \\192.168.0.4\PICKING_1 from Commander.
7. It is roughly once per day that this is occurring.
My questions are:
1. Is there a better way to configure the system to avoid printer spooler lockups?
2. Can we print directly from Bartender to printer (bypassing the Windows spooler)?
Thanks in advance.
Fernando Ramos MiracleModerator
Please sign in to leave a comment.