Troubleshooting the Thin On-Demand Print Client

For information on your Thin Client session, click on View | Diagnostics from the menu bar:

The Loftware Client Diagnostics dialog box is displayed.

Figure 2-M: Loftware Client Diagnostics dialog box

The Client Diagnostics box gives you information on the Labels, Layout and Scan Paths, as well as printer information. If you are still having trouble printing using the Thin Client On-Demand Printing module, read the following checklist before calling Technical Support.

1.  Is LPS running (service started or scanning in interactive mode)?

2.  Verify that the paths you have chosen for your labels, layout and the scan path are valid. If they are not, manually set the paths in the UNC paths section.

3.  Make sure that you have configured the right printer for the label.

4.  Verify that all server information is correct, such as the IP address, etc.

5.  Make sure that you can still test print the label from the label designer back on the server.

It is possible to configure printers with the Loftware Print Server running. The LPS monitors printer changes, and when it detects a change, the printer list is updated, and notifications are sent to the connected On-Demand Print Client(s).

Be aware that a problem could develop on the client-side if a printer is deleted on the server side, for example, an ODP Client attempting to print to the deleted printer would receive a display that states “No Printer Configured.”  Also, when the list of printers is updated because of a configuration change, if more than one printer of the same make and model printer exists, the default is to the first printer in the list that matches the loaded label. 

Example:  Say there are three Zebra 170XiIII printers configured on Printers 1, 5 and 7, the user is printing to Printer 5, and the printer configuration is changed.  The default printer then becomes Printer 1.  This may create a problem for a user who is attempting to print, and does not notice that the printer list has changed.  The label that was previously printing without any problems seems not to be able to print. This is another case in point where a Printer Alias can be very helpful, as the client user may be more apt to notice a change in the alias of the printer, as opposed to just a number.