Create a Remote Spooler (LPR) Connection
By using Line Printer Remote (LPR) protocol, you can configure Loftware Enterprise SP to spool to a print queue that is directly connected to a client computer by a wired or wireless connection. The device may be connected to the client computer by USB port, parallel port, serial port, or other means. Alternatively, if the device is not accessible to the Loftware Application Server and if a Remote Site has been defined for that computer, then you can configure Loftware Enterprise SP to print to a device that is accessible to the Remote Site via LPR protocol.
Note: Before you can use a remote spooler (LPR) connection with Loftware Enterprise SP, you must configure the client computer to support such connections.
Note: In a multi-site deployment A configuration of a Loftware environment that includes Loftware instances located at different sites within the same WAN. In a multi-site deployment, each Loftware instance acts as either a headquarters or a facility. of Loftware Enterprise SP, device connections can be created only at headquarters. They can be replicated to facilities by using synchronization, and they can be changed at facilities if allowed by the configuration. Remote Sites can be created at both headquarters and facilities to enable the use of a Loftware NiceLabel driver. For more information, see Using a Loftware NiceLabel Driver at a Facility.
To create a new remote spooler (LPR) connection, use this procedure.
- In Devices
> Device to create a new device.
- In the Device Model dialog box, do the following.
- Select a Family other than Server.
- Select a Model other than Image or PDF.
- Click OK.
- In the Connection tab, for Connection Type select TCP/IP and configure settings. For more information, see User Interface: TCP/IP Connection Type.
- If the device is not accessible to the Loftware Application Server via LPR protocol, for Remote Site browse and select the Remote Site from which the device is accessible via LPR protocol. Otherwise, no Remote Site is needed.
- For IP Address, enter the IP address or DNS name of the client computer to which the device is connected. Do not use the generic name localhost.
- For Protocol, select LPR. The IP Port is automatically changed to 515 and must not be altered.
- For LPR Queue, enter either the device name or the share name for the device. (Sharing the device is not required.) This field is not case-sensitive.
- Leave the Raw LPR check box selected. Clearing this option would allow the operating system driver to alter the print stream, which could have unpredictable results.
- Optional: For Document Name, you can enter a string that can include variables to format how print jobs from this device connection are identified in the Windows Server print queue. This option does not affect what appears on the printed label.
- In the Options, Media, and other tabs, configure device family-specific options.
- In the Properties pane, enter a Description of the device.
- In the ribbon, click Save
and then enter a Device Name in the Save dialog box.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square brackets, ampersands, plus signs, commas, semi-colons, and tildes. Additionally, the following characters are permitted but cannot begin or end the name: spaces, double quotation marks, single quotation marks, hyphens, underscores, periods, and grave accents. For letters, the case that you specify is displayed, but case is ignored when Loftware Enterprise SP interprets a name. If you will be installing the Loftware Enterprise SP application on a computer running Windows Server, and transferring data between Loftware Enterprise SP instances, see the "Transferring Data in a Compressed File" section of the Loftware Enterprise SP Data Transfer Guide.
- In Control Panel in Windows or Windows Server, ensure that the driver used by the device is Windows Generic/Generic Text Spooler.
Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information,