Lantronix ETS Reference Manual - 7:  Tcp/ip Host Setup

7-1

7:  TCP/IP Host Setup

The EZWebCon configuration software is the easiest way to configure teh Server. See your Installation 

Guide for more information on using the EZWebCon software. 

Servers servicing TCP/IP print queues must have the TCP/IP protocol enabled (the default). To verify that 

TCP/IP is enabled, enter the List Protocols command. 

The server must have an IP address before configuration; see your Installation Guide for more information. 

Any host wishing to access the ETSwill have to be informed of this IP address, which is typically configured 

in the UNIX /etc/hosts file or via a nameserver. 

Note:

One of the most common causes of IP network problems is duplicate IP 

addresses. Please make sure that your ETS has a unique IP address.

7.1   Selecting A Printing Method

The ETS provides three major TCP/IP printing methods: Berkeley remote LPR and Reverse Telnet (RTEL) 

host software and sockets. All methods provide queueing of jobs if the ETS is busy with another job. If 

custom queueing software has been designed, raw TCP/IP or Telnet socket connections can be made 

directly to the ETS ports. Instructions for all three methods are provided in the following sections. Please 

read through the entire configuration procedure before beginning.

Note:

See the man pages included with the distribution CD-ROM for a full discussion 

of RTEL functionality and configuration.

LPR

LPR allows the ETS to look like a UNIX host that can print files. It is the 

recommended way of printing because it is easy to set up and requires no 

additional host software. However, not all machines support the lpr system 

(notably machines running UNIX based on System V instead of BSD).

Note:

The ETS cannot implement all lpr options; the print job information is not 

available until the print job is completed.

Printing with LPD is also easy to set up, but LPD has a few significant 

restrictions. First, control information about the print job is sent after the print 

data has been sent, so options like binary characteristics and formatting cannot 

be applied. Second, the banner page is printed after the job instead of before it. 

Finally, because the Server is not actually spooling the print data locally, only 

one copy of the job will be printed regardless of the number of copies 

requested.