User guide
Table Of Contents
- Contents
- About This Document
- Introduction
- Installation
- Getting Started
- Before You Begin
- Printing a Configuration Label — External ZebraNet 10/100 Print Server
- Printing a Network Configuration Label — Internal ZebraNet 10/100 Print Server and Wireless Print Servers
- Configuration of Wireless Securities
- View Wireless Status through the Control Panel
- Determining the Active Print Server
- Assigning an IP Address on any Print Server
- Setting and Monitoring Alerts on any Print Server
- .
- Checking Print Server Configuration Settings
- Enabling Protocols
- Defaulting ALL Print Servers
- Using WebView
- Using ZebraNet Bridge
- Using a ZPL Command
- Defaulting the ZebraNet 10/100 Print Server on the 105SL, S4M, PAX4 and External Devices
- Defaulting the Wireless Print Server on the S4M
- Defaulting the Print Servers on the ZM400 and ZM600 Printers
- Defaulting the Print Servers on the ZP Series, LP/TLP 2824 Plus, and G-Series Printers
- Defaulting the Print Servers on the HC100 Printers
- Defaulting the Print Servers on the 105SL, PAX4, Xi4, and ZE500 Printers
- Defaulting the Print Servers on the ZT210 and ZT220 Printers
- Defaulting the Print Servers on the ZT230 Printers
- Printing Queues
- Using Printing Protocols
- ZebraLink WebView
- Print Server Web Pages
- Control Panel
- Hardware Troubleshooting
- Troubleshooting the External 10/100 Print Server
- Troubleshooting the Internal ZebraNet 10/100 Print Server
- Troubleshooting the Wireless Print Server
- ZebraNet Bridge Discovery or Configuration Problems
- Unable to Print
- Unable to Configure Device
- HP JetAdmin or HP Web JetAdmin
- Wireless Error Messages
- General Wireless Issues
- Encryption and Authentication Issues
- IP Issues
- Frequently Asked Questions
- Glossary
- Index
Printing Queues
Berkeley Software Distribution (BSD)-Style Print Queue
80
P1043301-002 02/28/2012
Berkeley Software Distribution (BSD)-Style Print Queue
BSD is a version of the UNIX OS that distributes software that includes TCP/IP.
Configuring the Print Queue
For remote BSD-style LPD printing, add the print server as a remote printer in the
/etc/printcap database to each host printing to any print server. You can add printcap options as
needed. If you are unfamiliar with these options, consult the printer documentation.
The entry looks similar to this:
local_print_queue_name|[printer_model_and_manufacturer]:\
:lp=:mx#0:rm=ZebraNet_name:\
:rp=remote_print_queue_name:\
:sd=path_to_spool_directory:lf=just log_file_name
local_print_queue_name — This defines the name of the printcap entry. It is used by
the LPR/LPD utilities to specify which printcap entry is being referenced. Additional printcap
entries can be added as needed for different queue types. Each entry must have a unique
local_print_queue_name and a different spool directory to work properly. When you are ready
to print, use the local_print_queue_name that matches the data type of the file to be printed.
ZebraNet_name — This is the name (alias) of the ZebraNet print server. This must be the
same name as entered in the /etc/ hosts file or your NIS or DNS system. An IP address may
also be used here.
remote_print_queue_name — This entry determines the ZebraNet port where the print
job will be printed and optionally specifies ASCII printing that must end for LF1.
path_to_spool_directory — This is the path to a directory where the print jobs will
be spooled for this queue. You must create a unique spool directory for each printcap entry.
log_file_name — This is the path to a file where error information from the LPD will be
logged.
Important • You must be logged in as root.
Example • Your printcap entries might look similar to this:
Ascii_files|form.feed.Queue_on_Port_1:\
:lp=:mx#0:rm=pserver1:rp=MYQUEUELF1:\
:sd=/usr/spool/myqueuelf1:\
:lf=/usr/spool/myqueuelf1/queue.log
Important • Each printcap entry must have a different spool directory to work properly.