Sei sulla pagina 1di 122

ETS4P4 Terminal Server

Installation Guide

Thank you for purchasing this Lantronix ETS Ethernet Terminal Server. As the newest addition to our successful Ethernet terminal server family, the ETS uses software for multiprotocol Ethernet connections that has over 5 years of real-world feedback and development behind it. Lantronix is constantly improving the capabilities of our products, and we encourage you to take advantage of new features through our FREE software upgrades (available via ftp over the Internet or BBS.) Our Flash ROM products, including this ETS, provide the simplest means for upgrades and installation. I hope you find this manual easy to use, and thorough in its explanation of the powerful features you can now access on your network.

Brad Freeburg President

Contents

Introduction
Overview...........................................................................1-1 Configuration ................................................1-1 Software ..........................................................1-2 About the Manuals ..........................................................1-2

Installation
Overview...........................................................................2-1 ETS Components..............................................................2-1 Installation ........................................................................2-2 Selecting a Location for the ETS ..................2-2 Connecting to the Ethernet...........................2-2 Connecting a Terminal..................................2-3 Supplying Power ...........................................2-3 Was the Installation Successful? ....................................2-3

Getting Started
Overview .......................................................................... 3-1 Command Syntax ............................................................ 3-2 IP Address Configuration .............................................. 3-3 Using a Directed Ping Packet ...................... 3-2 Using a BOOTP or RARP Reply.................. 3-4 Using the Command Line Interface............ 3-5 Remote Console Logins .................................................. 3-5 EZCon Logins ................................................ 3-5 TCP/IP Console Connections...................... 3-6 VMS Console Connections........................... 3-7 Incoming Logins .............................................................. 3-8 Serial Port Logins ............................................................ 3-8

Outgoing Sessions
Overview .......................................................................... 4-1 Initiating a Connection ................................. 4-1 Pausing/Resuming a Session ...................... 4-2 Disconnecting a Session................................ 4-3 Logging out of the ETS ................................. 4-3

ii

Services
Overview...........................................................................5-1 Services..............................................................................5-1 Attributes ........................................................5-2 Characteristics ................................................5-3 Protocols..........................................................5-4 Displaying Current Services ..........................................5-4

AppleTalk Configuration
Overview...........................................................................6-1 Bitronics Interface ............................................................6-1 Macintosh Service Configuration ..................................6-2 AppleTalk Zones..............................................................6-2 Printing From AppleTalk ...............................................6-3 LaserPrep ........................................................6-3 Printing Bitmap Graphics.............................6-3

LAN Manager Configuration


Overview...........................................................................7-1 Windows NT Users .........................................................7-1 DLC Configuration........................................7-2 NetBIOS Configuration.................................7-6 Windows NT Troubleshooting ....................7-8

iii

LAT Configuration Configuration


Overview...........................................................................8-1 Printing Directly to a Port...............................................8-1 PostScript Printing...........................................................8-3 Printing Using DCPS Software ......................................8-4

NetWare Configuration
Overview...........................................................................9-1 EZCon................................................................................9-1 Creating NDS Print Queues ...........................................9-2 Creating Bindery Print Queues......................................9-5 Using QINST ..................................................9-5 NetWare Queue Password .............................................9-7 PCL and Other Binary Printing .....................................9-7 PostScript Printing...........................................................9-7

iv

10

TCP/IP Configuration
Overview...........................................................................10-1 LPR on Generic UNIX Hosts..........................................10-2 Notes About LPR .............................................................10-4 LPR on AIX Hosts..........................................10-5 LPR on HP Hosts ...........................................10-7 LPR on SCO UNIX Hosts .............................10-9 LPR on Solaris Hosts .....................................10-11 LPR on ULTRIX Hosts ..................................10-11 LPR on Windows NT ....................................10-12 RTEL Functionality..........................................................10-16 TCP Socket Connections .................................................10-17 PostScript Printing from TCP/IP ..................................10-17

11

Additional Configuration
Overview...........................................................................11-1 System Passwords ...........................................................11-1 Privileged Password......................................11-1 Login Password..............................................11-2 Simple PostScript Configuration ...................................11-3 Serial Port Parameters.....................................................11-4 Parallel Port Parameters .................................................11-5 Port Access........................................................................11-6

Technical Support

Troubleshooting

Pinouts

Updating Software

Specifications

Index Warranty Declaration of Conformity

vi

Introduction

Overview

1 - Introduction 1.1 Overview


The Ethernet Terminal Server (ETS4P4)connects computing equipment such as personal computers, terminals, modems, or printers to an Ethernet network. The ETS communicates using the AppleTalk (EtherTalk), IPX (NetWare), LAN Manager (NetBIOS/NetBEUI), LAT, and TCP/IP protocols. Each server provides an AUI port, a BNC (10BASE2) port, and an RJ45 (10BASE-T) port for connections to the network. The ETS4P4 provides 4 RJ45 serial ports and 4 DB25 parallel ports to provide connections to devices on the network. The ETS supports a device on each port and the Ethernet simultaneously. It is congurable and can offer its attached devices as services to the network, and conversely, can provide connections to other devices on the network. NOTE: All ports can be used simultaneously for printer and terminal connections.

1.1.1 Conguration
It is possible, depending on the network, to power up the ETS and have it work properly with no additional conguration on the ETS. However if host conguration is required, the EZCon conguration software (shipped with the ETS on the distribution CD-ROM) will guide you through conguration using a point-and-click interface. NOTE: Instructions for using EZCon are included on the CD-ROM. EZCon is also available on the Lantronix FTP and BBS servers (See Appendix D, Updating Software).

1-1

About the Manuals

Introduction

Although EZCon is the recommended way to congure the server, the unit may also be congured using any of the following methods: By entering commands from a serial port connection By logging into the ETS over the network via AppleTalk, NetWare, Telnet, LAT, or NCP/TSM Via BOOTP replies from a TCP/IP network host; these replies may be used to dene the IP address, loadhost, and download lename Via RARP replies from a TCP/IP host; these replies may be used to dene the IP address By downloading a conguration le from a TCP/IP, LAT, or NetWare host at boot time

1.1.2 Software
The executable code for the ETS is stored in Flash (rewritable) ROM; therefore, software does not need to be downloaded each time the ETS boots. Downloading host software is only needed to update the code in the Flash ROM with a new version of the software. See Appendix D, Updating Software, for instructions on downloading new software into the ETS.

1.2 About the Manuals


This manual explains how to install, congure, and use the ETS. For detailed conceptual explanations, both a PostScript and a browsable HTML version of the ETS/EPS Reference Manual are available on the distribution CD-ROM. In addition, the Reference Manual is available at the Lantronix World Wide Web site, http://www.lantronix.com.

1-2

Installation

Overview

2 - Installation 2.1 Overview


This chapter describes how to install the ETS in a network. It assumes that you have a basic understanding of how to install devices in a network. Read this entire section completely before continuing.

2.2 ETS Components


The front panel of the ETS4P4 has 4 RJ45 ports. Each side panel of the ETS4P4 has 2 DB25 ports. Figure 2-1: ETS4P4

2-1

Installation

Installation

The back panel of the ETS has an AUI port, a 10BASE2 port, a 10BASE-T port, and a power plug. The ETS has seven LEDs on the top panel: PWR, LNK, POL, OK, NET, RCV, and XMT. The following table describes the LED functionality: Table 2-1: LED functionality
LED Power LED Polarity LED Good Link LED OK LED Network LED Parallel LED Serial LED Function Indicates that the unit has power. Indicates that the signal polarity is reversed on the wire. Indicates that the 10BASE-T cable has a good link with the network. Indicates that the unit is functioning properly. Indicates Ethernet activity. Indicates that the parallel port is active. Indicates that the serial port is active.

2.3 Installation
2.3.1 Selecting a Location for the ETS
When choosing a location for the server, keep in mind the environmental restrictions discussed in Appendix E.

2.3.2 Connecting to the Ethernet


The ETS has dedicated network ports for AUI, 10BASE2, and 10BASE-T. The ETS must be connected to a single Ethernet to function correctly, and will not function correctly if connected to more than one physical Ethernet port. The ETS must have a valid Ethernet connection to boot. If it detects a network fault, it will not boot. To boot the ETS without attaching it to the network, connect a terminated MAU to the AUI port or the 10BASE2 port or connect the 10BASE-T port to a disabled port on a hub. 2-2

Installation

Was the Installation Successful?

2.3.3 Connecting a Terminal


The ETS designates port 1 as a console port. A terminal may be connected to the console port to receive diagnostic and initial conguration messages. NOTE: The default serial port settings are 9600 baud, 8 bit characters, and no parity. Refer to Appendix C, for more information.

2.3.4 Supplying Power


Before supplying power to the ETS, be sure that only one physical Ethernet port is used. Plug the power cable into the ETS and then into the wall. The ETS goes through 2 steps to begin normal operation: 1. It runs through a set of power-up diagnostics for approximately 12 seconds. The group of 7 LEDs shows varying patterns corresponding to the test being run. It tries to obtain TCP/IP conguration information via BOOTP and RARP. This takes approximately 15 seconds if no hosts answer the requests. During this step, the OK LED blinks approximately 3 times per second and the NET LED blinks occasionally, as network requests are transmitted.

2.

2.4 Was the Installation Successful?


If the ETS appears to be working (OK LED blinking slowly) and the unit is connected to the network, there are a couple of ways to conrm that the unit is visible to network hosts: If the ETS has an IP address, ping it from a TCP/IP host. The EZCon utility (provided on the distribution CDROM) can be used to show available print servers.

When you are satised that the ETS is working properly, proceed to Chapter 3, Getting Started. If the server does not boot properly, see Appendix B, Troubleshooting. 2-3

Getting Started

Overview

3 - Getting Started 3.1 Overview


This chapter covers the steps needed to get the ETS on-line and running. There are 3 methods to log into the ETS and begin conguration. 1. 2. 3. Incoming (remote) Logins: EZCon is the preferred method of login and conguration. Remote Console Logins: TCP/IP users can connect to port 7000 via Telnet. Serial Port Logins: Users can connect a terminal directly to the serial port, log in, and use the command line to congure the unit.

It is important to consider the following points before logging into and conguring the ETS: The ETSs IP address must be congured before any TCP/IP functionality is available. For instructions on setting the IP address, see page 3-2. Only one person at a time may be logged into the remote console port, regardless of the protocol being used. This eliminates the possibility of several people simultaneously attempting to congure the ETS. Although all other login sessions may be disabled, remote console logins cannot be. Therefore the system manager will always be able to access the unit. Logging into the remote console port does not automatically create privileged user status. You must use the Set Privileged command to congure the unit. The remote console port is password protected. Default login password: access Default privileged password: system NOTE: For more information on System Passwords, see page 11-1. 3-1

Command Syntax

Getting Started

3.2 Command Syntax


Set/Dene commands appear frequently in this manual; therefore, it is important to note the difference between them. Set makes an immediate change, but is not permanent. Conversely, Dene makes a permanent change, but doesnt take effect until the ETS is rebooted or until the affected port is logged out. The Clear and Purge commands work similarly to the Set and Dene commands. Clear removes an item immediately, but does not make a permanent change. Purge removes an item permanently, but it doesnt take effect until the unit is rebooted. Strings must be enclosed in quotes. If they are not, they will be converted to all uppercase. If you need to add any character other than a letter (A-Z, a-z), you will need to locate the character on an ASCII chart and enter that number as a hexadecimal value. NOTE: For more information on the Set/Define and Clear/Purge commands and similar command constructs, refer to the ETS/EPS Reference Manual on the distribution CD-ROM.

3.3 IP Address Conguration


The ETSs IP address must be congured before any TCP/IP functionality is available. To set the IP address, the following methods can be used: a directed Ping packet, a BOOTP or RARP reply, commands entered at the command line (Local>) interface, or via EZCon (PC and Macintosh users only). All methods of setting the IP address are discussed in the following sections; choose the method that is most convenient for you. To access the ETS, hosts must know the ETSs IP address. This is typically congured in the hosts /etc/hosts le (UNIX) or via a nameserver. For conguration instructions, refer to the hosts documentation.

3-2

Getting Started

IP Address Configuration

3.3.1 Using a Directed Ping Packet


If the ETS has no IP address, it sets its address from the rst directed IP ICMP (ping) packet it receives. To generate such a packet, create an entry in the host's ARP table. The following gure shows how to create an entry in the hosts ARP table. Note that this requires superuser privileges. Substitute the intended IP address for the nnns and the hardware address for the xxxs of the server. Figure 3-1: Adding to the ARP Table for UNIX hosts
# arp -s nnn.nnn.nnn.nnn xx:xx:xx:xx:xx:xx

Figure 3-2: Adding to the ARP Table for Windows NT and Windows 95 hosts
# arp -s nnn.nnn.nnn.nnn xx-xx-xx-xx-xx-xx

NOTE: The ARP command will not work from Windows NT or Windows 95 hosts if it is the first entry in the ARP table. If there is no other entry in the ARP table, ping a node on the network to add an entry in the table. Then ping the server: Figure 3-3: Ping Command
unix% ping nnn.nnn.nnn.nnn

NOTE: If a router is between the server and the ARP host, this procedure wont work. When the server receives the ping packet, it notices that its own IP address is not currently set and sends out broadcasts to see if anyone else is using this address. If no duplicates are found, the server uses this IP address and responds to the ping packet. NOTE: The ETS will not save the IP address permanently; it is set temporarily to enable EZCon to communicate with the server, or to allow an administrator to telnet into the ETS remote console port. 3-3

IP Address Configuration

Getting Started

To save the IP address, telnet to the remote console port and specify the ETSs IP address and 7000 as the port number. The ETS will display the remote console port prompt ( # ). In order to successfully log into the port, the login password must be entered at this prompt. The default login password is access. To change this password, see System Passwords on page 11-1. To make the IP address permanent, use the Dene Server IPaddress command. Figure 3-4: Telnetting to the Console Port
% telnet nnn.nnn.nnn.nnn 7000 Trying nnn.nnn.nnn.nnn Connected to nnn.nnn.nnn.nnn Escape character is ^] # access (not echoed) Lantronix ETS Version n.n/n (yymmdd) Type Help at the Local_> prompt for assistance. Enter Username> xxxx Local> SET PRIVILEGED Password> system (not echoed) Local>> DEFINE SERVER IPADDRESS nnn.nnn.nnn.nnn

NOTE: At the Username> prompt any name can be entered to identify the current user.

3.3.2 Using a BOOTP or RARP Reply


At boot time a host-based BOOTP or RARP server can respond to an ETS request for an available IP address. For information about conguring the BOOTP or RARP servers, see the host documentation. Keep in mind that many BOOTP daemons will not reply to a BOOTP request if the download lename in the conguration le does not exist. If this is the case, create a le with the same pathname specied in the conguration le.

3-4

Getting Started

Remote Console Logins

By default, the ETS will attempt BOOTP and RARP queries. You can disable these queries by doing either of the following: Within EZCon, use the Maintenance:Server Boot Parameters menu. At the Local> prompt (accessible via EZCon, Telnet/ Rlogin, or by connecting a terminal to the serial console port), enter the Dene Server BOOTP Disabled and Dene Server RARP Disabled commands.

3.3.3 Using the Command Line Interface


To get to the command line, you may either connect a terminal to the console port and press Return or log into the ETS via EZCon. A Username> prompt will be displayed. After you enter a username, you will get the Local> prompt. To set the IP address at this prompt, you need to be the privileged user. See Privileged Password on page 11-1. Once youve obtained privileged access, use the Set/Dene Server Ipaddress command: Figure 3-5: Set/Dene Server IPaddress
Local>> DEFINE SERVER IPADDRESS nnn.nnn.nnn.nnn

If the Boot> prompt appears when you press Return, the ETS has experienced a boot problem. See Appendix B, Troubleshooting.

3.4 Remote Console Logins


3.4.1 EZCon Logins
The EZCon software, shipped with the ETS on the distribution CD-ROM, is the easiest way to log into and congure the unit. EZCon guides you through conguration using a point-and-click interface. NOTE: NetWare users must be running Windows version 3.1 or later with the NetWare VLM or a Winsock compliant TCP/IP stack. 3-5

Remote Console Logins

Getting Started

UNIX, Macintosh, Windows/Windows NT, and Novell NetWare versions of EZCon are shipped with the ETS on the distribution CD-ROM. To use the CD-ROM, refer to the instructions on the CD-ROM case. To install EZCon, refer to the appropriate EZCon README le. All instructions for using EZCon are listed in each README le. For assistance once EZCon is running, refer to the EZCon on-line help.

3.4.2 TCP/IP Console Connections


The ETS enables a TCP/IP user to congure the server via a single Telnet connection to the remote console port. The remote console port is designated as port 7000: Figure 3-6: TCP/IP Remote Console Login
% telnet nnn.nnn.nnn.nnn 7000 Trying nnn.nnn.nnn.nnn Connected to nnn.nnn.nnn.nnn Escape character is ^] # access (not echoed) Lantronix ETS Version n.n/n (yymmmdd) Type Help at the Local_4> prompt for assistance. Enter Username> xxxx

NOTE: The # prompt requires the login password be entered before the connection is allowed to succeed. The default login password is access. To change this password, see page 11-2.

3-6

Getting Started

Remote Console Logins

3.4.3 VMS Console Connections


From a VMS host machine, a connection to the remote console port can be established using NCP or TSM. First the node must be congured in the NCP database as shown below. Note that the NCP name cannot exceed six characters. NOTE: The parameters in the following table are examples of user-supplied parameters. These parameters will be different for you. Table 3-1: NCP Remote Console Login
$ RUN SYS$SYSTEM:NCP NCP> SHOW KNOWN CIRCUIT Known Circuit Volatile Summary as of <date time> CircuitState QNA-0 NCP> NCP> SET NODE server_name Node Address Node Name (1.1-63.1023): 13.241 (1-6 characters): server_name on

NCP> SET NODE server_name SERVICE CIRCUIT QNA-0 NCP> SET NODE server_name HARDWARE ADDRESS 00-80-A3-xx-xx-xx NCP> CONNECT NODE server_name # access (not echoed)

Lantronix ETS Version n.n/n(yymmdd) Type Help at the 'Local_4>' prompt for assistance. Enter Username> xxxx

NOTE: Note that this defines the server only in the temporary database. Use define commands to make a permanent entry. Once the node has been created in the database, the CONNECT command can be used to establish a session. See the NCP and TSM documentation for additional information on how to congure the NCP database and how to establish the remote console connection. 3-7

Incoming Logins

Getting Started

3.5 Incoming Logins


Incoming logins can be made using the EZCon application. Incoming LAT and TCP/IP logins can also be made using the commands entered at the Local> prompt. By default, incoming LAT connections are disabled and Telnet connections are enabled. To change these settings, use the Set/Dene Server Incoming command described in the Command Reference chapter of the ETS/EPS Reference Manual.

3.6 Serial Port Logins


Serial port logins can be made by attaching a terminal to the console port and pressing the Return key. If the unit is not yet congured, or if the ETS could not boot, a Boot prompt is displayed. This prompt enables you to enter a special set of commands, called Boot Conguration Program (BCP) commands, which are discussed in Appendix B. If the unit passes its power-up diagnostics and completes the boot procedure, the Local> prompt should be displayed. See the Command Reference chapter of the ETS/EPS Reference Manual for the complete ETS command set.

3-8

Outgoing Sessions

Overview

4 - Outgoing Sessions 4.1 Overview


The ETS4P4 server allows local serial users to connect to hosts on the network via LAT or TCP/IP. There are 3 ways to manipulate sessions: initiating, pausing/resuming, and closing.

4.1.1 Initiating a Connection


4.1.1.1 TCP/IP 4.1.1.1.1 Telnet To start an outgoing Telnet session, type Telnet at the Local prompt, followed by either the hosts name or its numeric IP address. Figure 4-1: Opening a Telnet Connection
Local> TELNET nnn.nnn.nnn.nnn

4.1.1.1.2 Outgoing Session Support A nameserver host can be specied to allow text TCP/IP hostnames to be resolved, and a default domain name to use in case a domain is not specied. Specifying a gateway host allows TCP/IP connections to other connected network segments. Figure 4-2 shows an example of the commands needed to congure the nameserver, domain, and gateway. Figure 4-2: Outgoing Session Conguration
Local>> DEFINE SERVER NAMESERVER nnn.nnn.nnn.nnn Local>> DEFINE SERVER IP DOMAIN weasel.ctcorp.com Local>> DEFINE SERVER GATEWAY nnn.nnn.nnn.nnn

NOTE: Backup hosts can be specified in case the primary nameserver or gateway fails; see the ETS/EPS Reference Manual for details.

4-1

Overview

Outgoing Sessions

The TCP/IP security table can be used to restrict incoming or outgoing TCP/IP connections. Managers can restrict connections by address or network on a port by port basis. See the ETS/EPS Reference Manual, or use the Help Set IPSecurity command to see the servers on-line help. 4.1.1.2 LAT To connect to a LAT service, type the word connect followed by the name of the desired host or service. The example below shows how to connect to the service named modem. Figure 4-3: Connection to a LAT Service
Local> CONNECT modem

NOTE: A service is a resource accessible to network hosts. For more information on using services, see Chapter 5. NOTE: To use LAT you must obtain a LAT license number from your dealer or Lantronix Sales. To allow LAT on your ETS Define Protocol LAT License command and reboot the server. To view available LAT nodes and services, enter Show Node or Show Services at the Local prompt.

4.1.2 Pausing/Resuming a Session


To return to the Local> prompt from a session, press the <Break> key or a user-dened Local switch character. To return to the last-used session from local mode, use the Resume command or either the Forward or Backward switch characters.

NOTE: For more advanced pausing and resuming functionality, refer to the ETS/EPS Reference Manual.

4-2

Outgoing Sessions

Overview

4.1.3 Disconnecting a Session


To disconnect a session, use the Disconnect command. This closes the last-used session, and leaves any others intact. If the user logs out (or is logged out by the administrator) all sessions are closed. The Show Session command shows all open connections for the current user. The session numbers displayed can be used with the Disconnect and Resume commands. Global and per-port session limits are provided to restrict the number of sessions a user can initiate. They are congurable with the Set Server Session Limit and Set Port Session Limit commands, respectively.

4.1.4 Logging out of the ETS


To log out of the ETS, press Ctrl-D or type Logout at the Local> prompt. NOTE: This will close all existing sessions.

4-3

Services

Overview

5 - Services 5.1 Overview


A service is a resource accessible to network hosts; for example, an AppleTalk user may queue print jobs to a service. Services control which protocols can use the ETS ports and how these ports appear to network users. In general, there has to be at least one service associated with a port before the port can be available to network users.

5.2 Services
The ETS offers a default service on each port. The service names are ETS_xxxxxx_yy where xxxxxx represents the last six numbers of the units Ethernet address and yy is the port name, for example S1 or P1. NOTE: The default service names are based on the server name; therefore the server name must be no more than 13 characters. The default services on the serial ports have the LAN Manager, NetWare, and TCP/IP protocols enabled. LAT is disabled by default on services provided by the ETS because many network managers object to the frequent LAT service announcements. To modify a default service, use the Set/Dene Service command with any of the attributes, characteristics, and protocols discussed in the following sections. If you modify the service name, keep in mind that service names are not case-sensitive, may be up to 16 alphanumeric characters long, and cannot include spaces. NOTE: Each service must be associated with at least one port. To associate a port with a service, use the Set/Define Service Ports command. If different service characteristics are necessary for printing from different types of host machines, multiple services all pointing to the same physical port can be created. The services can have their own unique characteristics. 5-1

Services

Services

5.2.1 Attributes
5.2.1.1 Service Name Each service has a name. 5.2.1.2 EOJ (End-of-Job) or SOJ (Start-of-Job) String Each service may have an End-of-Job or Start-of-Job string (or both). EOJ strings will be sent to the printer after every print job; SOJ strings will be sent to the printer before each print job. These strings are typically used to force the printer into a particular mode (such as PostScript or PCL). When specifying a string, use the following syntax: Figure 5-1: Examples of EOJ and SOJ Strings
Local>> DEFINE SERVICE backupprinter SOJ startchar Local>> DEFINE SERVICE backupprinter EOJ \23\4e\9atext

NOTE: The commands that you may want or need to enter in EOJ and SOJ strings are printer-specific; therefore they are not covered in this manual. NOTE: If you are using PostScript printing on an auto-sensing printer, you may not need to enter EOJ or SOJ strings to force the printer into PostScript mode; enabling the PostScript characteristic (see page 5-3) should do this. For more details, refer to your printers documentation. 5.2.1.3 Ident String Each service may have an identication string. This string typically contains a more verbose description of the service and is displayed by LAT when a Show Services command is issued. However, it is ignored by all other protocols. 5.2.1.4 Rating The rating describes the current state of the service. A non-zero value means the service is available. Zero means that the service is either in use or not available. 5.2.1.5 Ports The port list shows which port(s) the service is associated with. 5-2

Services

Services

5.2.2 Characteristics
These options specify how the ETS appears to network hosts and how it treats print data. 5.2.2.1 Banner This parameter only affects ETS banner pages when printing via LPD or NetWare. If a host generates its own banner, the ETS treats it as print data. By default, the ETS adds a banner page to LPD and NetWare jobs. 5.2.2.2 Binary If the binary option is specied, the ETS will not perform character processing on the data. By default (binary disabled) the ETS expands linefeeds into carriage return/linefeeds and performs tab expansion for LPD jobs. The binary option should be enabled for printing graphics jobs. 5.2.2.3 PostScript If enabled, the ETS sends a small PostScript job to the printer before the print data to force auto-selection printers into PostScript mode. It also attempts to conrm that the printer nished a job before starting the next one. If the printer attached to this service will be used only for PostScript, this option must be enabled. 5.2.2.4 PSConvert This characteristic allows a PostScript printer attached to the ETS to print non-PostScript jobs. When a le is queued to a service with the PSConvert attribute enabled, the le is encapsulated within a PostScript job. PSConvert is disabled by default. 5.2.2.5 TCP Port The TCP Port characteristics associates a numeric TCP socket (between 4000 and 4999) with the service. Connections to this socket will be accepted only if the service is currently available. This is an 8-bit clean connection. 5.2.2.6 Telnet Port The Telnet Port characteristic associates a numeric TCP socket (between 4000 and 4999) with the service. Telnet IAC interpretation will be done on the connection. Connections to this socket will be accepted only if the service is currently available. 5-3

Displaying Current Services

Services

5.2.3 Protocols
Each service has a protocol list associated with it; this list controls which protocols can access the service. Protocol parameters include AppleTalk, LAN Manager, LAT, NetWare, and RTEL (TCP/IP). To enable all protocols on a service use multiple Dene Service commands: Figure 5-2: Enabling All Protocols on Service Backupprinter
Local>> DEFINE SERVICE backupprinter APPLETALK ENABLED Local>> DEFINE SERVICE backupprinter LANMANAGER ENABLED Local>> DEFINE SERVICE backupprinter LAT ENABLED Local>> DEFINE SERVICE backupprinter NETWARE ENABLED Local>> DEFINE SERVICE backupprinter RTEL ENABLED

NOTE: To use LAT you must obtain a LAT license from your dealer or Lantronix and use the Set/Define Protocol LAT License command on your ETS.

5.3 Displaying Current Services


To examine a service's characteristics, issue the Show Service command: Figure 5-3: Showing Service Characteristics
Local> SHOW SERVICE backupprinter CHARACTERISTICS Service: backupprinter Ident: ETS Serial Port Rating: 255 Ports: 1

Characteristics: Queueing Rtel Connections Appletalk Netware Enabled Groups: 0 SOJ: startchar EOJ: endchar

5-4

AppleTalk Configuration

Overview

6 - AppleTalk Conguration 6.1 Overview


The following sections cover print conguration for AppleTalk hosts. The examples below show how to congure the ETS using commands entered at the command line interface (Local> prompt); however, the easiest way to congure the server is to use the EZCon point-and-click interface. A Macintosh version of the EZCon software are shipped with the ETS on the distribution CD-ROM. Macintosh users may use either the AppleTalk or the TCP/IP version of the EZCon software. All instructions for using EZCon are listed in each README le. For assistance once EZCon is running, refer to the EZCon on-line help.

6.2 Bitronics Interface


The ETS advertises its printers as LaserWriters; therefore, printing from a Macintosh requires a PostScript printer and bidirectional communication with that printer. The ETS supports the Bitronics interface (IEEE 1284 nibble mode). This interface, created by Hewlett-Packard, is an extension to the standard Centronics interface. Printers that support Bitronics (for example, the HP LaserJet 4 and greater family) allow bidirectional communication via the parallel port. To enable Bitronics on an ETS parallel port, use the following commands: Figure 6-1: Enabling Bitronics
Local>> DEFINE PORT n BITRONICS ENABLED Local>> LOGOUT PORT n

NOTE: The printer must support Bitronics and the Bitronics mode must be enabled on the printer. For the HP LaserJet 4 and greater, enable the ADV FNCTNS option in the parallel menu.

6-1

Macintosh Service Configuration

AppleTalk Configuration

6.3 Macintosh Service Conguration


To print from a Macintosh, you will need to enable both AppleTalk and PostScript. In Figure 6-2 a parallel service (ETS_PRT) is created using a Set/Dene Service command. Figure 6-2: Enabling AppleTalk and PostScript on a Service
Local>> DEFINE SERVICE backupprinter APPLETALK ENABLED POSTSCRIPT ENABLED Port 3

Once youve created the service, it should be visible in the Chooser of any Macintosh that is in the same zone as the ETS. If you have multiple zones on your network, the service will appear in the default zone specied by the AppleTalk router. Once you locate the service in the Chooser, select it and complete the appropriate setup options. Close the Chooser window and send a test page to the Macintosh service. NOTE: Macintosh computers must have the LaserWriter driver installed; if it is not installed, LaserWriters will not be available in the Chooser.

6.4 AppleTalk Zones


If the ETS is attached to a network without an AppleTalk router, all devices should be visible to all Macintosh Chooser clients. Note that the ETS will not accept AppleTalk print jobs for 60 seconds after booting while it listens for the nonexistent router. NOTE: Macintoshes that do not support EtherTalk will need a LocalTalk-to-EtherTalk router to use the ETS. If there is a router on the network, the ETS will appear in the default zone specied by the router. The zone name can be changed if the default zone is not the desired zone by using the following commands: Figure 6-3: Setting the AppleTalk Zone
Local>> DEFINE PROTOCOL APPLETALK ZONE radon_lab

6-2

AppleTalk Configuration

Printing From AppleTalk

6.5 Printing From AppleTalk


6.5.1 LaserPrep
The LaserPrep application saves bandwidth by making les much smaller. All Macintoshes printing to the ETS must be running the same version of LaserPrep; otherwise print jobs can be lost, as reloading the LaserPrep le repeatedly can prevent jobs from printing reliably.

6.5.2 Printing Bitmap Graphics


Ensure that the laser printer being used is congured to use 8-bit characters. If special characters or bitmaps are not printing correctly, it is typically because the printer is congured to use 7-bit characters. If les that contain embedded bitmap graphics print incorrectly, it is because the bitmaps are actual binary data. Binary data cannot be printed via serial or parallel interfaces. Most major application packages have provisions to print using either binary postscript (for printers connected to the network via LocalTalk) or hex postscript (for printers connected to the network via a serial or parallel port). If the application you are using does not have this provision contact your application vendor. There might be an upgrade patch available that adds the hex postscript function.

6-3

LAN Manager Configuration

Overview

7 - LAN Manager Conguration 7.1 Overview


The EZCon conguration software is the easiest way to setup print queues on the ETS. Windows/Windows NT versions of EZCon are shipped with the ETS on the distribution CD-ROM. All instructions for using EZCon are listed in each README le. For assistance once EZCon is running, refer to the EZCon on-line help. NOTE: Windows for Workgroups cannot reliably print jobs to the ETS via LAN Manager. Windows for Workgroups users should spool print jobs to a Windows NT host and print from that machine. NOTE: Printing using an LPD client is the preferred method for sending print jobs to the ETS. To print using the TCP/IP protocol see the LPR on Windows NT section on page 10-14. The following sections cover DLC and NetBIOS conguration for LAN Manager hosts. These instructions are designed for Windows NT.

7.2 Windows NT Users


The ETS must be added as a Windows NT printer before it can accept print jobs from a Windows NT host. Windows NT users can print using TCP/IP, the DLC protocol or the NetBIOS protocol. DLC conguration is simpler than NetBIOS conguration; however, NetBIOS is more exible. Both methods are discussed in the following sections. NOTE: The ETS does not support NetBIOS over TCP/IP.

7-1

Windows NT Users

LAN Manager Configuration

7.2.1 DLC Conguration


To use the DLC protocol, the DLC characteristic must be associated with a service. The DLC characteristic may be associated with only one service on any given ETS. To associate DLC with a service, use the Set/Dene Service DLC command. Figure 7-1: Associating DLC with PCL Service
Local>> DEFINE SERVICE ETS_PRT DLC ENABLED

NOTE: The following steps are for Windows NT 4.0 users. 1. 2. 3. Double-click the Printers icon in the Control Panel. Double-click the Add Printer icon. In the window that appears select My computer. Click Next. Figure 7-2: Selecting Your Printer Management

7-2

LAN Manager Configuration

Windows NT Users

4.

Select the Add Port button. Click Next. Figure 7-3: Adding a Port

Figure 7-4: Select Hewlett-Packard Network Port.Adding a HP Network Port

5. 6. Click New Port.

7-3

Windows NT Users

LAN Manager Configuration

7.

Enter the Service name. Figure 7-5: Entering the Server Name

8.

Select the manufacturer and printer type. Figure 7-6: Selecting the Printer Type

7-4

LAN Manager Configuration

Windows NT Users

9.

Enter the queue name. Figure 7-7: Entering the Printer Name

10. If applicable, choose Shared and select the type of operating system that the printer will be working with. (This is not recommended until the print queue is conrmed to be working.) Figure 7-8: Sharing the Printer

7-5

Windows NT Users

LAN Manager Configuration

11. Test the printer. Figure 7-9: Printing a Test Page

7.2.2 NetBIOS Conguration


Ensure that the LAN Manager characteristic is enabled on your service. To print from NetBIOS, you will need to redirect a port. Redirecting allows the user to use a service on the ETS as if it were on the host machine. Choose one of the LPT ports to redirect (typically the ports to choose from will be LPT1, LPT2, LPT3, or LPT4). Before you select a port to redirect, ensure that it doesnt currently have a printer connected to it. Double-click the DOS Command Prompt icon to open a DOS session. At the DOS prompt, use the NET USE command to indicate that the LPT port will be redirected to the ETS service. Figure 7-10: Net Use Command
C:> NET USE LPTn: \\ETS_xxxxxx\ETS_PRT

7-6

LAN Manager Configuration

Windows NT Users

The Windows NT node will attempt to connect to the ETS. If it cannot connect to the ETS, it will inform you of the problem. At this point, all references to LPTn (the port specied with the NET USE command in Figure ) will go to the service that you created. For testing purposes, you can try to use a copy command, if the ETS is ready to accept data. To make the LPT redirect permanent, use the following command. Figure 7-11: Making Redirect Permanent
C:> NET USE /PERSISTENT:YES

When the host is rebooted, the LPT redirect will be remembered and the host will automatically attempt to connect to the ETS. Exit the MS/DOS shell. Follow the instructions for adding a printer from the Printers Control Panel listed in DLC Conguration section on page 7-2. Remember when you reach Figure 7-3 you will be adding an LPT port instead of a Hewlett-Packard Networking port. NOTE: If the printer driver isnt already installed, youll need the Windows NT installation media.

7-7

Windows NT Users

LAN Manager Configuration

7.2.3 Windows NT Troubleshooting


If youve followed the setup instructions listed in this chapter, Windows NT printing should run smoothly. However, there are two potential problems: When Windows NT determines that insufcient progress is being made on a print job, it will automatically time out (force you to abort or retry) print jobs. By default, the timeout period is set to 45 seconds. If you have a slow printer, this timeout period may not be long enough; Windows NT may time out your print job when its queued to the ETS. To change the timeout period, see the Settings dialog box in Windows NT. NOTE: Editing the timeout period on all known versions for Windows NT does not actually change the 45 second timeout period. When a timeout occurs, Windows NT will try to restart the entire job. If you are unable to change your timeout period, try using LPR instead. Windows NT supports printing via AppleTalk and LAN Manager. The ETS and NT AppleTalk implementations are not compatible at this time; the ETS cannot accept AppleTalk jobs from Windows NT hosts.

7-8

LAT Configuration

Overview

8 - LAT Conguration 8.1 Overview


The EZCon conguration software is the easiest way to congure LAT print queues on the ETS. UNIX, Macintosh, Windows/Windows NT, and Novell NetWare versions of EZCon are shipped with the ETS on the distribution CD-ROM. All instructions for using EZCon are listed in each README le. For assistance once EZCon is running, refer to the EZCon on-line help. NOTE: To use LAT you must obtain a LAT license from your dealer or Lantronix and use the Set/Define Protocol LAT License command on your ETS. LAT print queues can be created by printing to a port or printing to a service. Printing directly to a port requires no ETS conguration. Printing to a service requires some conguration, but it allows multiple printers to service the same VMS queue. Note that the LAT characteristic must be enabled on any service being used. NOTE: Printing directly to a port is the preferred method for printing to the ETS. If you would like a complete discussion on printing to a service, see the ETS/EPS Reference Manual.

8.2 Printing Directly to a Port


Printing directly to a port is a 2 step process. First, a LAT application port that references an ETS port must be created on the LAT host. The LAT application port is a device that allows programs to treat a LAT connection as a physical port for input and output. For example, a printer might be congured to use port LTA3419, which might be connected or mapped to port 1 of the ETS. The LAT port can be mapped to either a service or an exact port on the ETS. Second, a print queue that uses the LAT application port must be created.

8-1

Printing Directly to a Port

LAT Configuration

The following example shows how to create a LAT application port: Figure 8-1: Creating LAT Application Port
$ RUN SYS$SYSTEM:LATCP LATCP> CREATE PORT LTAnnn/APPLICATION LATCP> SET PORT LTAnnn/node=ETS_xxxxxx/port=Port_x LATCP> EXIT

The nnnn is any unused LAT port number (use the Show Ports command to see which port numbers are in use). VMS users can then use port LTAnnnn as a port to the ETS. LATCP ports are not permanently congured on a host. To create the required LAT devices after each host reboot, add the necessary commands to the SYS$MANAGER:LAT$STARTUP.COM le. Note that LAT terminal device characteristics may have to be changed to correctly print some les. For example, the VMS terminal driver will change form feeds into an equivalent number of line feeds by default. To disable this behavior, enter the following command: Figure 8-2: Disabling Line Feeds
$ SET TERMINAL/PERM/FORM LTAnnn:

NOTE: See the VMS documentation for more information about terminal characteristics. To create and start a LAT queue on the host that uses this LAT application port, enter the following: Figure 8-3: Creating and Starting the Queue
$ INITIALIZE/QUEUE/START/ON=LTAnnn:/PROCESSOR=LATSYM /RETAIN=ERROR queue_name

8-2

LAT Configuration

PostScript Printing

A print request would then look like: Figure 8-4: Creating a Print Request
$ PRINT/QUEUE=queue_name filename.txt

8.3 PostScript Printing


Using PostScript printers with LAT queues adds two extra steps to the host queue setup; a PostScript form and a reset module need to be created on the host. The reset module will contain the Ctrl-D that the printer needs to nish and eject the job. To create the PostScript form use the following commands where formnum is any unused form number. Use Show Queue/Form/All to see the form numbers that are currently in use. Figure 8-5: Creating a PostScript Form
$ DEF/FORM POSTFORM formnum /STOCK/=DEFAULT/WIDTH=4096/WRAP

In the gure above, the longer width prevents the spooler from truncating long (but legal) PostScript command lines. To create the reset module, use an editor to create a le named EOJ.TXT. Place a Ctrl-D (ASCII 0x4) in this le and insert it into the system device control library. Figure 8-6: Creating a Reset Module
$ LIBRARY/REPLACE SYS$LIBRARY:SYSDEVCTL.TLB EOJ.TXT

If the library does not exist, it must be created using the following command: Figure 8-7: Creating a Control Library
$ LIBRARY/CREATE/TEXT SYS$LIBRARY:SYSDEVCTL.TLB

8-3

Printing Using DCPS Software

LAT Configuration

Finally, the INIT/QUEUE command creates the queue itself. Note the addition of the form specication and the reset module. Figure 8-8: Creating a Print Queue
$ INIT/QUEUE/START/DEFAULT=(NOFEED,NOFLAG,FORM=POSTFORM) /ON=LTAnnn: /PROCESSOR=LATSYM/RETAIN=ERROR/SEPARATE=(RESET=EOJ) ETS_POST

A print request would then look like this: Figure 8-9: Creating a Print Request
$ PRINT/QUEUE=ETS_POST filename.ps

8.4 Printing Using DCPS Software


The DCPS software supplied by DEC requires a bidirectional data path. This is only available on the parallel port if the printer supports the Bitronics extensions to the Centronics interface. For more information, see Bitronics Interface.

8-4

NetWare Configuration

Overview

9 - NetWare Conguration 9.1 Overview


The following sections cover print conguration for NetWare hosts. The easiest way to congure the server is to use the EZCon point-and-click interface. The examples in this chapter show how to configure the ETS using commands entered at the command line interface (Local> prompt). Instructions for conguring NDS print queues on the ETS are outlined in the Creating NDS Print Queues section. To create NDS print queues, you must be running NetWare version 4.0 or greater. If you are running versions 2.x, 3.x, or version 4.0 with bindery emulation, see the section titled Creating Bindery Print Queues. Bindery print queues may be congured using either EZCon, PCONSOLE, or QINST.

9.2 EZCon
Novell NetWare versions of EZCon are shipped with the ETS on the distribution CD-ROM. All instructions for using EZCon are listed in each README le. For assistance once EZCon is running, refer to the EZCon on-line help. NOTE: NetWare users must be running Windows version 3.1 or later with the NetWare VLM, or with a Winsock compliant TCP/IP stack.

9-1

Creating NDS Print Queues

NetWare Configuration

9.3 Creating NDS Print Queues


If you are using NDS, the Quick Set-Up option is the easiest way to create print queues with PCONSOLE. These steps must be done on each le server that will need access to the ETS queues. The following steps refer to NetWare v4.x or greater. 1. NDS Registration A. To register to use NDS, you must read and complete an NDS registration form. To receive a registration form either: Click NDS Registration on either the Lantronix home page (http://www.lantronix.com) or the Lantronix Product Information page, or Send email to nds-info@lantronix.com and you will receive a blank registration form via email.

NOTE: If you do not have Internet access, contact a Lantronix sales representative who will assist you with registration. See the Technical Support appendix for contact information. B. Once you have completed the form, click Submit on the web page or send the form back to nds@lantronix.com via email. C. To allow NDS on the ETS, enter the Dene Protocol NetWare DSLicense command using the string that you have received from Lantronix. Figure 9-1: Enabling NDS on the ETS
Local>> DEFINE PROTOCOL NETWARE DSLICENSE string

2.

PCONSOLE Print Queue Set-Up A. Log in as Admin on the le server you will be changing and type PCONSOLE at the F: prompt to start the utility. B. From the main menu choose Quick Set-Up.

9-2

NetWare Configuration

Creating NDS Print Queues

C. The Quick Set-Up window will appear. Enter the following information: Figure 9-2: The Quick Set-Up Window
Print Server: ETS_xxxxxx New Printer: ETS_xxxxxx_yy New Print Queue: backupprinter Print Queue Volume: ETS_serv Banner Type: Printer Type: Centronics Location: Marketing Interrupt: Port: n

The print server name (ETS_xxxxxx) is the name of your ETS. The new printer name (ETS_xxxxxx_yy) is the service name. The new print queue can be any name. The print queue volume is the name of the le server from which the printer receives print requests. The remaining elds can be left in their default settings. D. Once you have entered all elds in the Quick SetUp Window, press F10 to save the print queue information. 3. Print Server Conguration A. Use the Dene Protocol NetWare DSTree command to dene which directory service tree the print server is located on. Figure 9-3: Dening the Directory Services Tree
Local>> DEFINE PROTOCOL NETWARE DSTREE foodco

9-3

Creating NDS Print Queues

NetWare Configuration

B. Use the Dene Protocol NetWare DSContext command to dene the directory services context where the print server is located. Figure 9-4: Dening the Directory Services Context
Local>> DEFINE PROTOCOL NETWARE DSCONTEXT ou=kiwi.ou=exotic.o=fruit

NOTE: For an explanation of how the NetWare Directory Service tree is structured, see your host documentation. C. Enter the Show Protocol NetWare Access command to ensure that at least one of the le servers in the directory services tree is in the access list. By default the access list is set to Local which includes all le servers which are not across a router. To add to this list, enter the Dene Protocol NetWare Access command. Figure 9-5: Adding to the Access List
Local>> DEFINE PROTOCOL NETWARE ACCESS fileserver

D. Reboot the ETS using the Init Delay 0 command. Figure 9-6: Rebooting the Server
Local>> INIT DELAY 0

It may take up to two minutes for the print server to attach to the queue. 5. Enter the NETSTAT command. This will display information about le servers, printers, and queues that the print server has found. If a queue is in JobPoll then the print server has successfully attached to the queue. If the print server does not attached to the queue, refer to the NetWare Host Troubleshooting on page B-6.

9-4

NetWare Configuration

Creating Bindery Print Queues

9.4 Creating Bindery Print Queues


Bindery print queues can be created using either the QINST or PCONSOLE utilities. Instructions for using PCONSOLE are listed in the ETS/EPS Reference Manual.

9.4.1 Using QINST


The QINST utility requires that you use either the Supervisor (NetWare 2.2/3.11) or Admin (NetWare 4.0) account on the target le server. To use the utility, copy the QINST.EXE le from the distribution CD-ROM into the Public directory on the le server, ensure that it is in the executable path, and type QINST. When using NetWare version 4.0 and greater, the QINST program requires access to UNICODE tables to provide character translation. To ensure the utility runs properly, copy it into the NetWare Public directory or ensure that the PATH variable includes the required UNICODE tables. NOTE: If you wish to enable Bindery emulation, refer to your NetWare documentation.

9-5

Creating Bindery Print Queues

NetWare Configuration

The following example shows creating a Novell print queue named backupprinter. Figure 9-7: Creating Novell Print Queue
F:\> \Public\QINST Q-Install Logged in as ADMIN Installing on GONZO, NetWare V3.xx Enter the name of the print server. : ETS_xxxxxx <CR> Enter the name of the queue to create. : backupprinter <CR> Adding print queue backupprinter on volume GONZO_SYS Enter the service name on ETS_xxxxxx which will service this queue. : ETS_xxxxxx_yy Adding print server ETS_xxxxxx. Please wait... Attaching ETS_xxxxxx to backupprinter Adding print server ETS_xxxxxx_yy. Please wait... Attaching ETS_xxxxxx_yy to backupprinter

Ver. n.m.

Print queue installed successfully. Resetting ETS_xxxxxx. Resetting print server.

Install another queue [y/n]? n F:\>

Use the NPRINT command to print a job to the ETS. Figure 9-8: NPRINT Command
F:\> NPRINT C:\AUTOEXEC.BAT /QUEUE=backupprinter

9-6

NetWare Configuration

NetWare Queue Password

9.5 NetWare Queue Password


The default login password on the ETS is also used to log the ETS into NetWare le servers. If the login password on the ETS is changed, NetWare print queue setups must also be changed to reect the new password.

9.6 PCL and Other Binary Printing


The Binary attribute must be enabled. Figure 9-9 shows how to enable the Binary attribute. Figure 9-9: Enabling Binary Attributes
Local>> DEFINE SERVICE backupprinter BINARY ENABLED

NOTE: For more information about services, refer to Chapter 5.

9.7 PostScript Printing


The PostScript characteristic must be enabled on a service to print PostScript jobs. Figure 9-10: Enabling PostScript Attributes
Local>> DEFINE SERVICE backupprinter POSTSCRIPT ENABLED

NOTE: For more information about services, refer to Chapter 5.

9-7

TCP/IP Configuration

Overview

10 - TCP/IP Conguration 10.1 Overview


The following sections cover print conguration for TCP/IP hosts. The server must have an IP address before congurations can be made. (See IP Address Conguration on page 3-2 for details.) Any host wishing to access the ETS will have to be informed of this IP address, which is typically congured in the UNIX /etc/hosts le or via a nameserver. Refer to the host's documentation for additional information. The ETS provides two major methods of printing via TCP/IP: Berkeley remote-LPR and the RTEL host software. Both methods queue jobs on the host if the ETS is busy with another job. Instructions for host conguration for LPR and RTEL are described in the following sections. The remote-LPR software allows the ETS to look like a UNIX host that can print les. The Lantronix-supplied RTEL software, which requires installation and conguration on the host, provides more functionality than remote-LPR. It allows the hosts lp or lpr printing system to transparently use the ETSs print devices, and also allows the creation of named pipe devices on the host that map to the ETSs ports. See the documentation included with the distribution CD-ROM for a full discussion of RTEL functionality and conguration. Raw TCP/IP socket connections can be used with custom queuing software to create queues on the ETS.

10 - 1

LPR on Generic UNIX Hosts

TCP/IP Configuration

10.2 LPR on Generic UNIX Hosts


The Berkeley remote printing system is supported on many machines and is simple to congure for the ETS. Add the host print queue name into the /etc/printcap, and then specify the remote node name (the host name of the ETS) and the ETS service name. NOTE: There are slight variations in LPR configuration for AIX, HP, SCO UNIX, Solaris, ULTRIX, and Windows NT hosts; after reading this section, refer to the following sections for platform-specific configuration information. NOTE: Neither Windows for Workgroups or Windows 95 support LPR directly, but there are third party solutions available. For a list of third party solutions, see Technical Support FAQ on the Lantronix web site, http://www.lantronix.com. To add a print queue for an ETS, add the ETS's name and IP address to the /etc/hosts le: Figure 10-1: Adding Name and IP Address
nnn.nnn.nnn.nnn
ETS_xxxxxx

Edit the /etc/printcap le and add an entry of the following form: Figure 10-2: Editing /etc/printcap File
ETS_PRT|Printer on LAB ETS:\ :rm=ETS_xxxxxx:\ :rp=ETS_xxxxxx_yy:\ :sd=/user/spool/lpd/ETS_PRT:

Note that the punctuation shown is required and whitespace should be avoided within each option. The example creates a queue named ETS_PRT. The rm parameter is the name of the ETS in the host's address le, the rp parameter is the name of the service as it exists on the ETS, and the sd parameter species the name of a directory used to hold temporary spooling les.

10 - 2

TCP/IP Configuration

LPR on Generic UNIX Hosts

The spooling directory will have to be created using the mkdir command and should be world writable. Figure 10-3 shows how to create a spooling directory: Figure 10-3: Creating Spooling Directory
# mkdir /usr/spool/lpd/ETS_PRT # chmod 777 /usr/spool/lpd/ETS_PRT

In addition, the mx option may be used to allow unlimited size les to be printed and the sh option may be used to prevent header pages from being generated. See the host's documentation or man pages for more information on the format of the printcap le and how to create the spool directory. After adding the queue entry to the printcap le, it should be visible via the lpc status command: Figure 10-4: lpc Status Command
% lpc status ETS_PRT: queuing is enabled printing is enabled no entries no daemon present

Now you can print to the queue using normal lpr commands: Figure 10-5: Printing to Queues
% lpr -PETS_PRT /etc/hosts

10 - 3

Notes About LPR

TCP/IP Configuration

10.3 Notes About LPR


There are ve important things to note about the LPR printing method: Because of the way the LPR protocol is typically implemented on the host, the processing options and the banner page are sent after the job data itself. Because of this, the ETS will print a banner page at the end of a job, and cannot support most of the LPR options. If it is necessary to have the banner page at the beginning of the printout, install and use the RTEL software.

NOTE: The ETS prints banners at the end of each print job. The ETS cannot print multiple copies of the print job when the #<copies> lpr option is used. For example: Figure 10-6: lpr Multiple Print Option
lpr #3 /etc/hosts

If banners are not needed, they can be disabled using the ETS commands: Figure 10-7: Disabling Banners
Local>> DEFINE SERVICE ETS_xxxxxx_yy BANNER DISABLED

NOTE: See the Command Syntax section on page 3-2 for a description of the Set and Define command syntax. Many LPR spoolers are not intelligent about using multiple queues on one host. If two queues on the print host refer to two services on the same ETS, they must use separate spooling directories. If only the default directory is used, data from the two queues can be intermixed or sent to the wrong ETS service. No special purpose input or output lters can be used when printing via LPR. If lters are necessary, use the named pipe interface program in the RTEL software.

10 - 4

TCP/IP Configuration

Notes About LPR

10.3.1 LPR on AIX Hosts


Print queues on AIX hosts can be congured using either UNIX commands or the SMIT application. 10.3.1.1 Using UNIX Commands Using LPR on AIX hosts involves a slightly different conguration procedure. The queue conguration le is /etc/qcong and the format of the entry is different. Note the lack of colons (:) and the required white space: Figure 10-8: Adding to Printcap Entry
ETS_PRT: device = ETS_PRTd up = TRUE host = ETS_xxxxxx s_statfilter = /usr/lpd/bsdshort l_statfilter = /usr/lpd/bsdlong rq = ETS_xxxxxx_yy ETS_PRTd: backend = /usr/lpd/rembak

Note that the device name is simply the queue name with a d appended. 10.3.1.2 Using SMIT The System Management Interface Tool (SMIT) allows you to enable LPD printing and create print queues. 1. 2. 3. 4. At the host prompt type smit. From the main window in the application choose Print Spooling. Then choose Manage Print Server and Start the Print Server Subsystem (lpd daemon). In the Start the Print Server Subsystem dialog box, type both in the rst eld. Click OK. The lpd subsystem has been started will appear in the Output section of the next window. Click Done.

10 - 5

Notes About LPR

TCP/IP Configuration

To add a print queue use the following instructions. 1. 2. 3. 4. 5. From the main window choose Print Spooling. Then choose Manage Print Server and Manage Print Queues. Next, choose Add a print queue. From the dialog box that appears choose remote. From the next dialog box choose the type of remote printing. Add the following information to the Add a Standard Remote Print queue dialog box: Figure 10-9: Adding a Print Queue
Name of QUEUE to add: ETS_PRT HOSTNAME of remote server: ETS_xxxxxx Name of QUEUE on remote server: ETS_xxxxxx_yy TYPE of print spooler on remote server: BSD DESCRIPTION of printer on remote server: docuprinter

A dialog box will appear with the message Added print queue ETS_PRT. To print, the normal lp syntax is used: Figure 10-10: Printing to Queues
% lp -dETS_PRT filename

10 - 6

TCP/IP Configuration

Notes About LPR

10.3.2 LPR on HP Hosts


Print queues on HP hosts can be congured using either UNIX commands or the SAM application. NOTE: The maximum number of characters for the print server and service names is 13. 10.3.2.1 Using UNIX Commands To congure a print queue using LPR, become the superuser and issue the following commands: Figure 10-11: Conguring a Print Queue Using UNIX Commands
# /usr/lib/lpshut # /usr/lib/lpadmin -pETS_PRT -v/dev/null -mrmodel \ -ocmrcmodel -osmrsmodel -ormETS_xxxxxx -orpETS_xxxxxx_yy # /usr/lib/accept ETS_PRT # /usr/bin/enable ETS_PRT # /usr/lib/lpsched

Note that issuing the lpshut command will stop the HP spooling system, so this command should not be performed when print jobs are active. The lpadmin command adds to the print queue. The accept command tells the queueing system that the queue is accepting requests and the enable command enables the print queue so it can start printing. Finally, the lpsched command restarts the queuing system. To print to this queue, normal lp syntax is used: Figure 10-12: Printing to Queues
# lp -dETS_PRT filename

10 - 7

Notes About LPR

TCP/IP Configuration

10.3.2.2 Using SAM The System Administration Manager (SAM) allows you to create print queues. 1. 2. 3. 4. 5. At the HP prompt type sam. From the main application window choose Printers and Plotters. Click Open. Choose Printers/Plotters from the Printers and Plotters window. In the pull-down menu select Add Remote Printer/ Plotter from the Actions menu. Enter the following information: Figure 10-13: Conguring a Print Queue
Printer name: ETS_PRT (queue name) Remote system name: ETS_xxxxxx (printer name) Remote printer name: ETS_xxxxxx_yy (service name) Remote cancel model: rcmodel Remote status model: rsmodel

To print to this queue, normal lp syntax is used: Figure 10-14: Printing to Queues
# lp -dETS_PRT filename

10 - 8

TCP/IP Configuration

Notes About LPR

10.3.3 LPR on SCO UNIX Hosts


To congure a print queue using LPR, check to see if the Berkeley remote printing les and executable programs are installed on the host machine. If not, issue the mkdev command to install them. Figure 10-15: Installing Print Files
# mkdev rlp

This will install the Berkley remote printing les and executable programs. Note that this should only be done once. NOTE: The mkdev rlp command should only be entered once. If the command is used repeatedly, serious problems will result with the machine. If this occurs, contact SCO technical support. To create a remote printer, use the following command: Figure 10-16: Creating Remote Printers
# rlpconf

10 - 9

Notes About LPR

TCP/IP Configuration

This command will ask a series of questions and create a printcap entry for the specied queue. The process is shown in the following gure. Figure 10-17: Conguring the Remote Printer
Remote Printing Configuration Enter information for remote printers or local printers accepting remote printing requests Please enter the printer name (q to quit): ETS_xxxxxx_yy Is printer ETS_xxxxxx_yy a remote printer or a local printer? (r/ l) r Please enter the name of the remote host that ETS_xxxxxx is attached to: ETS_PRT The ETS_xxxxxx_yy is connected to host ETS_PRT. Is this correct? (y/n) y Would you like this to be the sys.default printer? (y/n) y Make sure your hostname appears in ETS_PRTs /etc/hosts.equivor or /etc/hosts:lpd file. Make sure ETS_xxxxxx_yy appears in /etc/printcap (in BSD format). Make sure ETS_xxxxxx_yy has a spool directory on ETS_PRT. Putting the printer in printer description file and creating spool directory... done Updating LP information... done

NOTE: When prompted for the printer name, keep in mind that it must match the service name on the print server. NOTE: If youd like to change the queue name at a later point, it can be changed by manually editing the printcap file. To print to this queue, normal lp syntax is used: Figure 10-18: Printing to Queue
# lp -dETS_PRT filename

10 - 10

TCP/IP Configuration

Notes About LPR

10.3.4 LPR on Solaris Hosts


NOTE: Due to problems in the Solaris queueing system, LPR is not reliable on Solaris machines. Users with Solaris hosts should use the Lantronix-supplied RTEL software. The following commands congure a BSD print queue on a Solaris 2.3 system. These commands require that you are the superuser and in the bourne shell. Figure 10-19: Creating a BSD Print Queue
# /usr/lib/lpsystem -t bsd ETS_xxxxxx_yy # /usr/lib/lpadmin -p ETS_PRT -s ETS_xxxxxx!ETS_xxxxxx_yy # /usr/lib/accept ETS_PRT # enable ETS_PRT

Figure 10-20: Printing to Queue


# lp -dETS_PRT filename

10.3.5 LPR on ULTRIX Hosts


ULTRIX hosts will need the following additional information added to the printcap entry. Figure 10-21: Adding to Printcap Entry
ETS_PRT|Printer on LAB ETS:\ :lp=:ct=remote:\ :rm=ETS_xxxxxx:\ :rp=ETS_xxxxxx_yy:\ :sd=/usr/spool/lpd/ETS_PRT:

The additional options will show that there is no physical device for this queue and tell the host that this is a remote connection.

10 - 11

Notes About LPR

TCP/IP Configuration

To print to this queue, normal lp syntax is used: Figure 10-22: Printing to Queue
# lpr -PETS_PRT filename

10.3.6 LPR on Windows NT


The following procedure congures an lpr print queue on Windows NT 4.0. NOTE: This installation assumes that the TCP/IP protocol, Simple TCP/IP services, and Microsoft TCP/IP printing have been installed in Windows NT. NOTE: Verify that you are able to Ping or Telnet the server from Windows NT before configuring the print queue. 1. 2. 3. Double-click the Printers icon in the Control Panel. Double-click the Add Printer icon. In the window that appears select My computer. Click Next. Figure 10-23: Select Printer Monitoring

10 - 12

TCP/IP Configuration

Notes About LPR

4.

Select the Add Port button. Click Next. Figure 10-24: Adding a Port

5.

Select LPR Port. Figure 10-25: Adding a LPR Port

6.

Click New Port.

10 - 13

Notes About LPR

TCP/IP Configuration

7.

In the following window enter the name or address of the ETS and the service name. Figure 10-26: LPR Dialog Box

8.

Select the manufacturer and printer type. Figure 10-27: Selecting the Printer Type

10 - 14

TCP/IP Configuration

Notes About LPR

9.

Enter the queue name. Figure 10-28: Entering the Printer Name

10. If applicable, choose Shared and select the type of operating system that the printer will be working with. (This is not recommended until the print queue is conrmed to be working.) Figure 10-29: Select Printer Sharing Mode

10 - 15

RTEL Functionality

TCP/IP Configuration

11. Test the printer. Figure 10-30: Printing a Test Page

10.4 RTEL Functionality


If the LPR method of printing is not adequate for an application (for example banners are needed before jobs or more exibility is needed in printing), Lantronix-supplied RTEL software can be congured on the host. Once the software is installed and connections to the ETS have been congured, normal Unix print commands and queue utilities (such as lpc and lpstat) can be used. NOTE: RTEL binaries are provided for many systems and source code is provided for use on non-supported systems. (See the Lantronix Web site, http://www.lantronix.com, for a list of the supported systems.) To print to the ETS using special formatting or using third-party software packages, it may be necessary to create print pipes on the host. The RTEL software provides this functionality by providing a UNIX namedpipe interface.

10 - 16

TCP/IP Configuration

TCP Socket Connections

To recreate the RTEL source les, copy the le RTEL_SRC.TAR from the distribution media to the UNIX host. If copying via the network, a binary copy must be performed. Untar the archive using the following command: Figure 10-31: Untarring the Archives
# tar xvf rtel_src.tar

There will be README les in the created directories that describe the contents of the RTEL distribution and documentation that describes the actual software functionality.

10.5 TCP Socket Connections


If custom queuing software has been designed on a host, raw TCP/IP or Telnet connections can be made directly to the physical ETS ports. Opening a TCP session to port 300n will form a connection to port n on the ETS. The 30nn range of ports is 8-bit clean. If Telnet IAC interpretation is needed, form a connection to port 200n. If the port is in use or its access is set to Local, the connection will be refused. NOTE: For more information about TCP socket connections, refer to the ETS/EPS Reference Manual.

10.6 PostScript Printing from TCP/IP


To print postscript jobs, the PostScript attribute must be enabled on the service being used: Figure 10-32: Enabling PostScript Attribute
Local>> DEFINE SERVICE ETS_xxxxxx_yy POSTSCRIPT ENABLED

A very common problem when printing PostScript jobs from UNIX queues is including non-PostScript data (i.e. header or banner pages) as part of the job. When printing from a UNIX host machine, verify that header and trailer pages are not sent. See the host's documentation for information on preventing header and trailer pages. 10 - 17

Additional Configuration

Overview

11 - Additional Conguration 11.1 Overview


This chapter discusses some additional ETS conguration. It includes the system passwords, postscript conguration, printer conguration, and port characteristics.

11.2 System Passwords


There are two important passwords on the ETS: the privileged password and the login password. NOTE: If you choose to change either password, the new password must be no more than 6 alphanumeric characters. For security purposes, you should use a mix of letters and numbers in each password.

11.2.1 Privileged Password


Changing any server or port setting requires privileged user status. EZCon will prompt you for the privileged password when it is needed. If you are not using EZCon, you will need to enter the Set Privileged command at the Local> prompt to become the privileged user. The default privileged password on ETS is system. Figure 11-1: Set Privileged Command
Local> SET PRIVILEGED Password> system (not echoed) Local>>

The prompt will change to reect privileged user status. Only one user can be the privileged user at a time. If another user is currently logged into the ETS as the privileged user, use the Set Privileged Override command to forcibly become the privileged user.

11 - 1

System Passwords

Additional Configuration

To change the privileged password, use the Set/Dene Server Privileged Password command. The following gure displays an example of this command. Figure 11-2: Changing Privileged Password
Local> SET PRIVILEGED Password> system (not echoed) Local>> DEFINE SERVER PRIVILEGED PASSWORD pie4me

11.2.2 Login Password


The login password is required for remote console logins and for password-protected serial ports. The default login password is access. To change the login password, use the Set/Dene Server Login Password command. The following is an example. Figure 11-3: Changing Login Password
Local> SET PRIVILEGED Password> system (not echoed) Local>> DEFINE SERVER LOGIN PASSWORD 82much

The login password is also used to log the ETS into NetWare le servers. If the login password is changed, NetWare print queue setups must also be changed to reect the new password. See the PCONSOLE instructions in the ETS/EPS Reference Manual.

11 - 2

Additional Configuration

Simple PostScript Configuration

11.3 Simple PostScript Conguration


Figure 11-4 creates a service for a PostScript printer on an ETS parallel port. Figure 11-4: Creating a Service for a PostScript Printer
Local>> DEFINE SERVER NAME BIOLAB Local>> DEFINE SERVICE BIOLAB_P1 LAT ENABLED Local>> DEFINE SERVICE BIOLAB_P1 IDENT BIOLAB PostScript Local>> DEFINE SERVICE BIOLAB_P1 POSTSCRIPT ENABLED Local>> DEFINE SERVICE BIOLAB_P1 NETWARE DISABLED Local>> INITIALIZE DELAY 0 (reboot now)

There are several important points to note in this example: LAT is enabled on this service and a descriptive identication string has been dened.

NOTE: To use LAT you must obtain a LAT license from your dealer or Lantronix and use the Define Protocol LAT license command on your ETS. The PostScript characteristic is dened on the service. The NetWare protocol is turned off on the service. NetWare le servers will not be allowed to use this service. Since all characteristics have been dened, rebooting the server will make them active. Rebooting also veries that the conguration has been properly stored in the Non-Volatile RAM.

11 - 3

Serial Port Parameters

Additional Configuration

11.4 Serial Port Parameters


Typically the only serial port parameters that will have to be changed are the baud rate, parity, ow control, and character size parameters. The default settings are 9600 baud, no parity, XON/XOFF ow control, and 8bit characters. To see the serial port characteristics, enter the Show/List Port Characteristics command: Figure 11-5: Serial Port Characteristics
Local>> list port 1 characteristics Port 1: Username: Char Size/Stop Bits: 8/1 Flow Ctrl: Parity: Access: Backward: Break Ctrl: Forward: Xon/Xoff None Remote None Local None Physical Port 1 (Idle) Input Speed: Output Speed: Modem Control: Local Switch: Port Name: Session Limit: Terminal Type: 9600 9600 None None Port_1 4 Soft()

Preferred Services:

(Lat) (Telnet)

Authorized Groups : 0 (Current) Groups : 0

Characteristics: Verify

Use the Help Set Port command to see a full listing of serial port options.

11 - 4

Additional Configuration

Parallel Port Parameters

11.5 Parallel Port Parameters


The only congurable parallel port parameter is the Printer Type characteristic. By default, the parallel ports have the following characteristics: Figure 11-6: Parallel Port Characteristics
Port 5 : Username: Physical Port 5(Idle)

Access: Backward: Break Ctrl: Forward:

Remote None Local None

Local Switch: Port Name: Session Limit: Printer Type: Not Connected

None Port_5 N/A Centronics

Printer Status:

Authorized Groups : 0 (Current) Groups : 0

Characteristics: Verify

If a printer that supports Bitronics mode (for example an HP LaserJet family) is connected to the ETS's parallel port, the Bitronics characteristic can be enabled on the port if necessary. Figure 11-7: Enabling Bitronics
Local>> DEFINE PORT 4 BITRONICS ENABLED Local>> LOGOUT PORT 4

11 - 5

Port Access

Additional Configuration

11.6 Port Access


The port access mode controls how the port will respond to network requests and input from external devices. The Dene Port Access command has the following parameters. LOCAL Network connections to this port are completely disabled but terminals may log into the ETS. This setting is useful for conguring and monitoring the ETS. Both local connections (logins on the serial port) and network connections (host-based print requests) are enabled. Only network connections are allowed. This is the default setting for the parallel port(s).

DYNAMIC

REMOTE

11 - 6

Technical Support

Overview

A - Technical Support A.1 Overview


If you are experiencing problems with the ETS or have suggestions for improving the product, please contact Lantronix Technical support at the address or phone number listed below. We are also available on the World Wide Web at http://www.lantronix.com and Internet electronic mail at support@lantronix.com.

A.2 Lantronix Problem Report Procedure


When you report a problem, please provide the following information: Your name, and your company name, address, and phone number Lantronix model number Serial number of the unit Software version (use the Show Server command to display) Network conguration, including the information from a Netstat command Description of the problem Debug report (stack dump), if applicable Status of the unit when the problem occurred (please try to include information on user and network activity at the time of the problem)

Technical Support: 800/422-7044 or 714/453-3990 Technical Support Fax: 714/450-7226 Internet: support@lantronix.com World Wide Web: http://www.lantronix.com BBS: 714/367-1051 FTP server IP address: 192.73.220.84

A-1

Troubleshooting

Overview

B - Troubleshooting B.1 Overview


This appendix discusses how to overcome a number of different types of problems. Please read this section before calling Lantronix Technical Support with a problem; the solution may be a simple one located in this appendix. If after reading this section you cant solve the problem, contact Lantronix or your dealer. Lantronix contact information is listed in Appendix A.

B.2 Power-up Troubleshooting


There are several possible error situations if the unit does not display the welcome message or the LEDs do not ash: Table B-1: Power-up Troubleshooting
Power/ Error Message Power-up diagnostic failure Power-up error detected

Error The LEDs will remain in one pattern and the console will not work. If the error is nonfatal, the ETS will boot but wont try to load the Flash ROM code. Instead it will print a diagnostic message to the serial port and display the Boot> prompt. The OK and Net LEDs will blink in unison two-three times per second. The Flash ROM is corrupt.

Diagnosis/Remedy Usually a hardware failure. Contact your dealer or Lantronix. Verify the Ethernet connection. Once booted and running normally, the OK LED will blink once every two seconds.

The ETS passes power-up diagnostics, but then attempts to download new code from a network host.

Both the OK and Parallel LEDs will blink in unison. You will need to reload Flash ROM. Refer to Appendix D, Updating Software.

B-1

Printing Problems

Troubleshooting

B.3 Printing Problems


Table B-2: Printing Troubleshooting
Areas to check Check the Physical Connection Explanation To test a non-PostScript printer use the Test Port n Count 100 command. This command will send 100 lines of test data out the port. If print data has been lost or corrupted on the serial printer, verify that RJ45 pins 4 and 5, transmit and receive ground, have both been connected to DB25 pin 7, signal ground. On a parallel printer, verify that a Lantronix-supplied parallel cable is being used. For PostScript printers, refer to PostScript Problems on page B-10. Verify Serial Flow Control Verify that the printer and the ETS agree on the method to be used for ow control. The ETS defaults to XON/XOFF ow control. See Chapter 11, for information on changing serial port settings. To verify that ow control is working, issue the Test Port command and take the printer off-line momentarily. This will cause the printer to stop accepting data and will ow control the ETS. When the printer is placed back on line, printing should continue with no disruption in the data. Verify Service Characteristics Use the Show Service Local Characteristics command from a network login to the ETS to see if the desired service is available. If the service rating is zero, the port is in use. Verify that the protocol list for the service in question has the appropriate protocols enabled.

B-2

Troubleshooting

Printing Problems

Areas to check Monitor the Queue Status and the Port Counters

Explanation On the host system, print a le using the appropriate print command. Then use the Show/Monitor Queue command to see if a queue entry appears in the ETS queued job list. If a queue entry never appears on the ETS, see the appropriate host troubleshooting section. Many operating systems will not release a second job to a queue, even if there are multiple ports associated with the ETS service. If an active queue entry appears, the next step is to verify that data is actually being sent to the port. Issue the command Monitor Port n Counters. If the output byte counter is incrementing, data is being sent to the print device. If not, verify the connection between the ETS and the printer.

B.3.1 LPD Host Troubleshooting


Table B-3: LPD Host Troubleshooting
Area to Check Verify that the ETS's IP address and name were entered properly in the hosts le. Verify that jobs which appear in the host queue reach the ETS. Explanation Telnet to or ping the ETS using the name found in the host le. Verify that the ETS's name is resolvable and that the ETS is reachable via the network. Become superuser on the host. Clear and reset the host queue using the following commands: abort queue_name, clean queue_name, enable queue_name, and start queue_name. These commands will kill the currently executing daemon, remove all old entries in the queue, enable the queue to accept new entries, and restart job processing.

B-3

Printing Problems

Troubleshooting

B.3.2 VMS Troubleshooting


By default, the LAT error message codes on the host are not translated into text error messages. If a LAT job fails and appears in the queue with an eight-digit hex result code, the code can be translated by issuing the following commands: Figure B-1: Translating LAT Error Codes
$ SHOW QUEUE/FULL/ALL queue_name (note the error code nnnnnnnn) $ SET MESSAGE SYS$MESSAGE:NETWRKMSG.EXE $ EXIT %Xnnnnnnnn

When conguring a LAT device on a VMS host machine using a port name, check the following: Table B-4: VMS Host Troubleshooting using a Port Name
Area to check Verify that the specied node name matches the servers node name. Verify that the specied port name matches the appropriate port name. Explanation Use the Show Server command on the ETS.

Use the List Port command on the ETS. The default port names are Port_n.

B-4

Troubleshooting

Printing Problems

When conguring a LAT device on a VMS host machine using a service, check the following: Table B-5: VMS Troubleshooting using a Service
Area to check Verify that the specied node name matches the servers node name. Verify that the service name used matches the appropriate service name. Verify that the service rating is nonzero. Explanation Use the Show Server command on the ETS. Use the Show Service Local Characteristics command on the ETS. Use the Show Service Local Characteristics command from a network login to the ETS to see if the desired ETS service is available. If the service rating is zero, the port is in use. Use the Show Service Local Characteristics command from a network login to the ETS to see if the LAT characteristic has been enabled on the service. To use LAT you must obtain a LAT license from your dealer or from Lantronix. Then use the Dene Protocol LAT License command on your ETS. Use the VMS command Show Queue/Full queue_name to see the queue characteristics.

Verify that the LAT characteristic has been enabled on the service.

Verify that LAT has been licensed on the ETS.

Verify that the LAT symbiont was specied as the queue process when the queue was created on the VMS host. If you are using DCPS, verify the bidirectional path to the printer and verify that the printer is locked into PostScript mode.

Lock the printer in PostScript mode and issue the Test Service PostScript Count n command. This command sends a job to the printer and waits for the response.

If a connection attempt has been unsuccessful when initially conguring a LTA device, the LAT host software may get confused. Deleting and recreating the LTA port is often required to clean things up.

B-5

Printing Problems

Troubleshooting

B.3.3 NetWare Host Troubleshooting


Table B-6: NetWare Host Troubleshooting (Bindery Mode)
Area to check Verify that the Bindery queue created manually using PCONSOLE was created correctly. Verify that the server and queue names appear and match the server and service name. Explanation

Either delete the queue and re-create the queue using QINST or re-verify the steps used to create the queue.
Run PCONSOLE and enter Bindery emulation mode. (If you are using NetWare 4.0, this can be done by pressing F4.)

The following section assumes that the Novell queue was created using PCONSOLEs Quick Set-Up option. If you experience NDS printing problems, try the following steps: Table B-7: NetWare Host Troubleshooting (NDS)
Area to check Verify that the NetWare access table will allow access to the specied le server. Verify that the login password on the ETS and the queue password on the le server match. Check the NetWare access list Explanation By default, only local (non-routed) le servers are scanned for queues. See page 9-2 for more information on manipulating the NetWare access lists. If the passwords do not match, the ETS will not be able to log into the le servers to scan for jobs. If there is a signicant delay between NetWare jobs, the delay may be a result of scanning too many le servers. This delay is often increased if the le servers are distributed across a wide area network. Congure the NetWare access list to only allow scanning for jobs on the le servers of interest. To congure the NetWare access list, see page 9-2.

B-6

Troubleshooting

Printing Problems

Area to check Verify that the print server has successfully attached to the queue.

Explanation Type NETSTAT at the Local> prompt. This will display information about leservers, printers, and queues that the print server has found. If a queue is in JobPoll then the print server has successfully attached to the queue. Type Show Protocol NetWare NDS. This command shows the tree and the context that you have congured, a failure code, and an NDS error code for each NDS server. DSTree is the directory service tree on which the print server is located. DSContext is the context where the print server is located and must match the context on le server. (The DSContext must be of the following form: ou=fruit.o=exotic) DSLicensed should be yes. Table and Table show the failure codes and the NDS error codes that may appear.

Verify that the DSTree, DSContext, and DSLicensed are correct.

Verify that the printer and queue changes that you have made propagate through the NDS tree.

It may take a few minutes for the changes to propagate through the NDS tree. If the print server doesnt attach, reboot the server.

B-7

Printing Problems

Troubleshooting

Table B-8: NDS Printing Errors

Failure Code 0 1

Failure Code Meaning Success

Remedy

Print server ran out of mem- Cycle power on the box. If the problem ory. persists, disable the unused protocols and change the NetWare access list to only include le servers which have print queues associated with them. Invalid resolved offset. Report the problem to Lantronix Technical Support.

2 3 4

Resolved name was referred Report the problem to Lantronix Technito another server. cal Support. No printers found for the print server. Check to make sure that there are printers for the print server and the printer names match the service names on the print server. Check to make sure that the printers have associated queues. Check to make sure there is a print server object congured with the same name as the print server. Check that the login password on the print server is the same as the password for the print server object. If the login password on the print server is the default (access) then there should be no password for the print server object.

5 6

No queue found for the printer. Login failed.

Authentication failed.

Print server can not attach to Check the directory services partitions, queue. replicas, and volumes to make sure that the le server where the queue actually lives has the information about the print server and printers.

B-8

Troubleshooting

Printing Problems

Table B-9: NDS Failure Code

Failure code 0 0xfffffda7

Failure code meaning Success Object could not be found in the given context.

Remedy

Check the print server name, dscontext, and dstree to make sure that the printer server is set up correctly with PCONSOLE.

0xfffffda5

The requested attribute could Use PCONSOLE to make sure that not be found. the print server has associated printers and that the printers have associated queues. DS Database is locked. An administrator is probably updating the database. Wait a few minutes and issue the Set Protocol NetWare Reset command. Make sure the password for the print server object under PCONSOLE is the same as the login password for the print server. If the login password on the print server is the default (access) then there should be no password for the print server object. If the login password is something other than the default, then the password for the print server object should match. The le server is probably requiring NCP packet signature which is not currently supported. The NCP packet signature level needs to be turned down so that it is not required from the server.

0xfffffd69

0xfffffd63

The password is invalid.

0xfffffd54

Secure NCP violation.

B-9

PostScript Problems

Troubleshooting

B.4 PostScript Problems


PostScript printers introduce their own set of problems, since they will silently abort jobs if they detect an error. The printer will typically accept the print job, process the job for a few seconds, and then return to the ready state without ejecting any paper or showing any error messages. The following procedures start at the most basic troubleshooting level, verifying the physical connection between the printer and the ETS and progressively work up to actual printing from the host system. Table B-10: PostScript Troubleshooting
Areas to Check Verify the Physical Connection Verify that the ETS is communicating with the printer. Explanation Check that the cables on the ETS are secure. To test a PostScript printer use the Test Port n PostScript Count 2 command where n is the port number. This command will generate 2 pages of PostScript data and send it to the port. If print data has been lost or corrupted on the serial printer, verify that RJ45 pins 4 and 5, transmit and receive ground, have both been connected to DB25 pin 7, signal ground. On a parallel printer, verify that a Lantronix-supplied parallel cable is being used. If the serial wiring is correct but characters are still lost, verify that both the printer and the ETS agree on the ow control method being used. By default, the ETS is congured for XON/XOFF ow control with 8-bit, no parity and 1 stop bit characters. See Chapter 11, for serial conguration options.

B - 10

Troubleshooting

PostScript Problems

Areas to Check Verify Service Characteristics

Explanation

Several common PostScript printing problems are service-based. Use the Show Service Local Characteristics command. In order for a service to be accessible from the network, its rating must be non-zero. If it is zero, the physical port is either inaccessible (access is dened to LOCAL) or is in use. Verify that the PostScript characteristic has been enabled on the service being used. In addition, verify that the protocol list for the service has the appropriate protocols enabled.

Monitor Port Counters

If PostScript jobs appear to print but nothing comes out of the printer, verify the amount of data sent from the host. Then use the Zero Counter All command to zero the counters. Issue the appropriate print command from the host system. After the job has completed, issue the Show Port n Counters command. The bytes output value should be approximately 870 greater than the size of the le on the host system. The extra bytes are from the PostScript handshaking that the ETS performs with the printer. As a last resort, replace the PostScript printer with a terminal attached to the serial port on the ETS and examine the data that appears on the terminal. Remember to disable the PostScript characteristic on the service using the Set Service ServiceName PostScript Disabled command. If this is not done, the port will hang waiting for an end-of-job character (<Ctrl-D>) to be transmitted from the terminal.

B - 11

PostScript Problems

Troubleshooting

B.4.1 AppleTalk Host Troubleshooting


Table B-11: AppleTalk Host Troubleshooting
Area to Check Verify that the printer is visible and can be selected in the Chooser. Verify that a consistent version of the LaserPrep le is used. Verify that both the printer and the ETS are congured to use 8bit characters and agree on the type of ow control in use. Verify that the LaserWriter driver is not corrupt. Explanation If it is not visible, the printer may be congured in the wrong zone. See page 6-2. If this is not possible, try testing from only one workstation to reduce version conicts until printing is working. See Chapter 11, for ETS port conguration. Refer to the printer's documentation for instructions on conguring the printer. If the queue was working and then stops, try reinstalling the LaserWriter driver. The LaserWriter driver modies itself to save conguration information and may become corrupt. Refer to PostScript Problems on page B-7. Lock the printer in PostScript mode and issue the Test Service PostScript Count n command. This command sends a job to the printer and waits for the response.

Verify bidirectional communication.

B - 12

Troubleshooting

Entering Commands at the Boot Prompt

B.5 Entering Commands at the Boot Prompt


The Boot Conguration Program (BCP) executes at power-up and provides the commands necessary to congure the ETS to boot up and function normally. The Boot Conguration Program stores parameters in the servers non-volatile memory. For example, a typical TCP/IP conguration might use the following commands: Figure B-2: BCP Command Examples
Boot> SET SERVER IPADDRESS nnn.nnn.nnn.nnn Boot> SET SERVER SOFTWARE /tftpboot/ETSP.SYS Boot> SET SERVER LOADHOST nnn.nnn.nnn.nnn Boot> SET SERVER SECONDARY nnn.nnn.nnn.nnn Boot> INIT 451 % Initialization begins in 5 seconds...

These commands set the ETSs address, set the software load le name, and set the load hosts IP address (as well as that of a backup loadhost). The server then reboots using the Init 451 command. (At this point the ETS attempts to load the le ETSP.SYS from the host at 192.0.1.188.) Until the server has been able to load its complete set of code from a load host, only a small subset of the servers full command set is available. Any unknown characters will end the command line and cause the command to be aborted.

B - 13

Entering Commands at the Boot Prompt Troubleshooting

The following table describes the commands that are available to you from within the Boot Conguration Program (BCP). Table B-12: Boot Conguration Program Commands
Command Help Init 451 Description Displays a one-page summary of the commands available and what they do. Reboots the ETS after it has been congured. If the ash is valid, this command loads the software from the ash. If the ash is invalid and it can nd the le you specied (with Set Server Software) it will load that le and then restart itself with full functionality. If there are no errors but the loadle is not found, the server will attempt to load continuously (with longer intervals between attempts.) If there are errors or if the <Return> key is pressed on the console, the BCP will be reentered. Enables or disables the sending of BOOTP queries during the boot sequence. Default is enabled. Species this servers IP address. Uses the standard numeric w.x.y.z format. Species the host to attempt to load the le from. ip_address should be in the standard numeric w.x.y.z format (no text names are allowed). Species the NetWare leserver to attempt to load the le from. Enables or disables the sending of RARP queries during the boot sequence. Default is enabled. Species whether the ETS always reloads the Flash. By default the server reloads the Flash only when it is invalid. Species a backup host to attempt to load the le from. ip_address should be in the standard numeric w.x.y.z format (no text names are allowed). The backup host will be queried if the primary host does not (or cannot) load the server. Enables or disables the startup messages.

Set Server BOOTP {Enabled, Disabled} Set Server IPaddress ip_address Set Server Loadhost ip_address

Set Server Netwserver leserver Set Server RARP {Enabled, Disabled} Set Server Reload Set Server Secondary ip_address

Set Server Silent

B - 14

Troubleshooting

Entering Commands at the Boot Prompt

Command Set Server Software lename

Description Species the name of the le to load. The ETS will automatically add ETSP.SYS to the lename you specify. Note that all protocols must have a lename specied (either the default or set by the user). The default is ETSP.SYS. For NetWare and TFTP loaders, you can specify the complete path name of the le (15 characters or fewer) if the le is located in a directory other than the default. For TFTP, the case of the lename must match that of the lename loaded onto your host computer.

Show Server

Show is used to display the current settings of the parameters. You should use this command before and/or after you issue other commands to see what the current setup is or has been changed to. This command is used to restore the ETS non-volatile RAM to its factory default settings. It will reset everything that is congurable on the server, including the units IP address.

Flush NVR

Flash

This command will force the ETS to download its operational code and reprogram it into Flash ROM. This is necessary, for example, if a new version of software is released and you wish to upgrade your units to this version. If the server cannot download the le, the code in Flash ROM will still be usable.

B - 15

Pinouts

Overview

C - Pinouts C.1 Overview


The ETS4P4 ports consist of 4 RJ45 serial ports and 4 DB25 serial ports.

C.2 Serial Information


Lantronix servers are RS-423 compliant, and are thus limited by the equipment at the remote end of the serial line. If the ETS is connected to an RS-232 device, it is subject to the RS-232 limits shown below. RS-232 lines are limited to 15m (50 ft.) in length at 9600 baud, and to 2m (6 ft.) at 115.2K baud, although they will generally work at longer lengths. The pinout of the RJ45 Serial Ports is shown below:

Figure C-1: Pinout of RJ45 Serial Ports


12345678

1 - RTS (out) 2 - DTR (out) 3 - TX+ (out) 4 - TX5 - RX6 - RX+ (in) 7 - DSR (in) 8 - CTS (in)

C-1

Serial Information

Pinouts

C.2.1 RJ45 to DB25


If you are connecting an RJ45 port to a DTE device (such as a terminal) that has a DB25 connector, you will need to use an RJ45-DTE DB25 adapter. To connect an RJ45 port to a DB25 connector on a DCE device (such as a modem), an RJ45-DCE DB25 adapter is required. The pinout information for both connections is displayed below. Figure C-2: Pinouts of RJ45-DB25 Connections
DTE - DB25 Adaptor (Gray) Pinout RJ45 Serial Port
CTS (in) DSR (in) RX+ (in) RXTXTX+ (out) DTR (out) RTS (out)

DCE - DB25 Adaptor (Blue) Pinout RJ45 Serial Port


RTS DTR TXD

Cable

RJ45-DB25 Adapter RJ45 (server)


1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 7 3 6 5
SG RXD DSR CTS

Cable

RJ45-DB25 Adapter RJ45 (server)


1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 7 2 20 4
SG TXD DTR RTS

DB25 (terminal)
4 20 2
CTS (in) DSR (in) RX+ (in) RXTXTX+ (out) DTR (out) RTS (out)

DB25 (modem)
5 8 3
CTS DCD RXD

8 7

6 5

8 7 6 5 4 3 2 1

8 7

6 5

8 7 6 5 4 3 2 1

64 53 42 3 2 1

64 53 42 3 2 1

NOTE: The arrows in Figure C-2 represent the direction of the signal. The ETS cable kit provides 8 prewired DCE-DB25 connectors (blue) and 4 unwired female DB25 adapters (gray). In most cases, the blue connectors will be used. If the modem device has a male connector, then a female DCE connector can be built from the using the gray adapters. Both the transmit and receive ground signals on the ETS connector are wired to the signal ground on a DB25 adapter. NOTE: The pinouts in Figure C-2 assume that the 8-conductor cable connecting the ETS and the adapter block is a swapped cable.

C-2

Pinouts

Serial Information

A crimper block is provided to connect both transmit and receive grounds from the RJ45 cable to the single signal ground on the DB25. The connector internally splices the two wires together and provides one wire into the DB25 connector as shown below: Figure C-3: Wire Splicer Sealed at this end RJ45 Tx Return RJ45 Rx Return DB25 Signal Ground

C-3

Serial Information

Pinouts

To splice the wires, cut off the end of the wire that does NOT extend through the connector and insert both wires into the connector. Make sure that the wire that does not extend through the connector is in as far as possible to ensure a solid connection. Make sure that the wire that does extend through the connector extends far enough on the other side to be inserted in to the DB25 connector. Carefully squeeze the connector using a pair of pliers to make sure it is fully latched.

C.2.2 RJ45 to DB9 (IBM PC Standard) Pinouts


If youre connecting an RJ45 serial port to a terminal with a DB9 (IBM PC Standard) connector, youll need to use an RJ45-DB9 adapter. To wire this type of adapter, refer to the diagram below. Figure C-4: Pinout of RJ45-DB9 Connection
RJ45 Serial Port
CTS (in) DSR (in) RX+ (in) RXTXTX+ (out) DTR (out) RTS (out) 8 6 7 5 6 4 5 3 42 3 2 1 8 7 6 5 4 3 2 1

Cable

RJ45-DB9 Adaptor DB9 RJ45 (terminal) (LRS)


1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 5 2 6 8 SG RXD DSR CTS 7 4 3 RTS DTR TXD

NOTE:
The arrows in this diagram represent the direction of the signal.

NOTE: Note that both the transmit and receive ground signals on the ETS connector are wired to signal ground on the DB9 adapter.

C-4

Updating Software

Overview

D - Updating Software D.1 Overview


Current software les are available on the distribution CD. Software updates and release notes for the ETS can be downloaded directly from the Lantronix development systems in one of three ways: via the Lantronix World Wide Web site at http://www.lantronix.com, using anonymous FTP through the Internet, and via dial-in modem. Comments and/or requests for help via email are welcome - send them to support@lantronix.com and they will be routed appropriately. Questions or comments regarding the ftp/download process itself can be sent to ftp@lantronix.com. Mail can also be sent from within the BBS menu access or from the Lantronix World Wide Web.

D.2 Updating Via the Web


The latest version of the ETSP.SYS can be downloaded from the Lantronix Web site. The following instructions will lead you through the web site to the software le. 1. 2. 3. 4. 5. On the homepage, http://www.lantronix.com, click on Free Software Updates. In the directory that appears choose pub/. Choose the server acronym from the next directory. Next, choose the software volume. Choose ETSP.SYS from the nal directory.

NOTE: As a result of Netscapes configuration, clicking on the software name will not allow you to download the file. To download the file from Netscape, you must save the file as a source document to your host.

D-1

Updating Using FTP

Updating Software

D.3 Updating Using FTP


The server software resides on the Lantronix FTP server (ftp.lantronix.com). The current IP address of the server is 192.73.220.84. This is subject to change at any time; the text name should be used if at all possible. Most of these les are binary data, so the binary option must be used to ftp whenever transferring the les. To log into the FTP server, use a username of anonymous and enter your full email address as the password. When connected to the Lantronix FTP server, the following text will be displayed: Figure D-1: Lantronix FTP Session
230-Welcome to the Lantronix FTP Server. 230230-IMPORTANT: Please get the README le before proceeding. 230-IMPORTANT: Set BINARY mode before transferring executables. 220230-Direct questions to support@lantronix.com or 1.800.422.7044 230-Questions about this ftp account only to ftp@lantronix.com 230230230 Guest login ok, access restrictions apply. Remote system type is UNIX. [your type will be displayed here] Using binary mode to transfer les. ftp>

All released les are in the pub directory. Always download the README le in the pub directory before downloading anything else; it contains a directory of available versions.

D.4 Updating Using the BBS


The Lantronix system uses high speed modems for the physical connection and allows le transfers using KERMIT, xmodem, ymodem, and zmodem. The modem phone number is (714) 367-1051. The account name is ets and the password is server. D-2

Updating Software

Updating Using the BBS

Remember that the download les (*.SYS) and executable images are image data and should only be transferred in binary mode. If binary mode is not used, the les will be corrupted. Figure D-2: Lantronix BBS System, New User Entries
SunOS UNIX (nexus) login: ets Password: server (not echoed) Last login: Mon Jun 5 13:21:13 from company.com SunOS Release 4.1.3_U1 (NEXUS) #2: Fri Dec 2 10:08:39 PST 1994 Welcome to the Lantronix BBS. Type h for help userid (new for new user): new Welcome, new user! Enter a userid, 1-12 characters, no spaces. Userid: bob Enter Passwd: platypus (not echoed) Confirm Passwd: platypus (not echoed) User Name: bob Terminal type (default=vt100): Email address, if any: bob@widgets.com

Figure D-3: Lantronix BBS System, Introduction Screen


Welcome to the NEW Lantronix Bulletin Board System. To access the files menu, type f at the main menu. At the files menu, type p to select a download protocol (a=ascii, k=kermit, x=xmodem, y=ymodem, z=zmodem) At the files menu, type l to list available software directories. Select the board name by entering its number. At any menu, press h to receive additional help. Press [Return] to continue:

D-3

Reloading ETS Software

Updating Software

D.5 Reloading ETS Software


The ETS stores its software in Flash ROM. This software controls the initialization process, the operation of the ETS, and the processing of commands. The contents of Flash ROM can be updated by downloading a new version of the operational software. The ETS can be reloaded from network hosts using NetWare, TCP/IP, or MOP. Reloading instructions are given beginning on page D-5. Regardless of which protocol is used to update Flash ROM, the following points are important: The Flash ROM software is contained in a le called ETSP.SYS, provided with the ETS on the distribution CDROM. The ETSP.SYS download le should be world-readable on the host, regardless of which download method is being used. In addition, there is an sixteen character length limit for the path name and a twelve character limit for the lename. Dene commands are used because conguration done with Set commands are cleared when the ETS boots. Use the List Server Boot command to check the ETS settings before using the Initialize Reload command.

NOTE: It is very important to check the ETS settings before using the Initialize Reload command; ensure that you are reloading the correct software file.

D-4

Updating Software

Reloading ETS Software

D.5.1 Reloading Sequence


If either BOOTP or RARP is enabled on the ETS it will request assistance from a BOOTP or RARP server before starting the download attempts. The ETS will then try TFTP, NetWare, and MOP booting, in that order, provided that it has enough information to try each download method. Downloading and rewriting the Flash ROM will take approximately two minutes from the time the Initialize command is issued. If more than two minutes has elapsed and the server has still not successfully booted, press the button on the front panel of the ETS. A brief page will be queued to the parallel port and printed, describing the problem. If the download le cannot be found or accessed, the ETS can be rebooted with the code still in Flash ROM. As noted in Chapter 2, the OK LED will blink quickly while the ETS is booting (and reloading code) and then slowly when it returns to normal operation. NOTE: If you experience problems reloading Flash ROM, refer to Troubleshooting Flash ROM Updates on page D-7.

D.5.2 NetWare
The ETSP.SYS le should be placed in the login directory on the NetWare le server. The ETS cannot actually log into the le server (since it knows no username or password); it can only access les in the login directory itself. On the ETS, specify the le server name, lename and path: Figure D-4: Reloading Flash ROM From NetWare
Local> SET PRIVILEGED Password> SYSTEM (not echoed) Local>> DEFINE SERVER NETWARE LOADHOST fileserver Local>> DEFINE SERVER SOFTWARE SYS:\LOGIN\ETSP.SYS Local>> INITIALIZE RELOAD

D-5

Reloading ETS Software

Updating Software

D.5.3 TCP/IP
Before the ETS downloads the new software, it will send BOOTP and/or RARP queries. (BOOTP and RARP queries are enabled by default; however, they can be disabled using the commands described on page B-14.) Next, the ETS will attempt to download the ETSP.SYS le using TFTP (Trivial File Transfer Protocol). If a host provides BOOTP or RARP support, it can be used to set the ETS's IP address and loadhost information. Add the ETS's name, IP address, hardware address, and download path and lename to the BOOTP or RARP le (usually /etc/bootptab). Some BOOTP and TFTP implementations require a specic directory for the ETSP.SYS le; in this case the path should not be specied in the bootptab le and the le must be placed in that directory. See your hosts documentation for instructions on how to congure the ETSP.SYS le in the directory. If BOOTP cannot be used to congure the ETS's IP parameters, congure them by hand using the following commands listed below. NOTE: For instructions on how to log into the ETS and enter these commands, refer to Chapter 10, TCP/IP Configuration. Figure D-5: Reloading Flash ROM From TCP/IP
Local> SET PRIVILEGED Password> SYSTEM (not echoed) Local>> DEFINE SERVER IPADDRESS nnn.nnn.nnn.nnn Local>> DEFINE SERVER SOFTWARE /tftpboot/ETSP.SYS Local>> DEFINE SERVER LOADHOST nnn.nnn.nnn.nnn Local>> LIST SERVER BOOT Local>> INITIALIZE RELOAD

The path and lename are case-sensitive and must be enclosed by quotation marks ( ). If attempting to boot across an IP router, the router must be congured to perform proxy arping for the ETS.

D-6

Updating Software

Troubleshooting Flash ROM Updates

D.5.4 MOP
Copy the ETSP.SYS le to the MOM$LOAD directory. The ETSP.SYS lename is the only parameter that the ETS needs to reload via MOP. Make sure the service characteristic is enabled on the host's Ethernet circuit, and then reload the server using the following commands: Figure D-6: Reloading Flash ROM From VMS
Local> SET PRIVILEGED Password> SYSTEM (not echoed) Local>> INITIALIZE RELOAD

NOTE: If an error message is displayed indicating an invalid record size on the VAX console, the ETSP.SYS file was not transferred in binary mode.

D.6 Troubleshooting Flash ROM Updates


Many of the problems that occur when updating the Flash ROM can be solved by completing the following steps: Figure D-7: Troubleshooting Flash ROM Updates
Protocol Area to Check Make sure the le is in the login directory. Since the ETS cannot actually log into the le server, it has very limited access to the server directories. Check the le and directory permissions. Make sure the loadhost name and address are specied correctly and that their case matches the case of the lenames on the host system. Ensure that the host has TFTP enabled; several major UNIX vendors ship their systems with TFTP disabled by default. The Ethernet circuit must have the service characteristic enabled. Verify that the MOM$LOAD search path includes the directory containing the ETSP.SYS le. Verify that the les were transferred in Binary mode.

NetWare

TFTP

MOP

D-7

Specifications

Power Requirements

E - Specications
E.1 Power Requirements
Adapter Input Voltage: Power Consumption: 110 Volts AC (domestic) 110/220 Volts AC (international) 12 Watts (maximum)

E.2 Temperature Limitations


Operating range: Storage range: 5 to 50C (41 to 122F) -40 to 66C (-40 to 151F)

Maximum temperature change per hour: 20C (36F) Rapid temperature changes may affect operation. Therefore, do not operate the ETS near heating or cooling devices, large windows, or doors that open to the outside.

E.3 Altitude Limitations


Operating: Storage: 2.4 km (8000 ft.) 9.1 km (30,000 ft.)

If operating the ETS above 2.4 km (8000 ft.), decrease the operating temperature rating by 1.8C for each 1000 m (1F for each 1000 ft.).

E.4 Relative Humidity Limitations


Operating: Storage: 10% to 90% (noncondensing) (40% to 60% recommended) 10% to 90% (noncondensing)

E-1

Index

A
AIX host configuration 10-5 AppleTalk PostScript printing 6-3 Troubleshooting B-12 AppleTalk zone, setting 6-2 Warranty information 1

Configuration options 1-1 Console connections TCP/IP 3-6 VMS 3-7

D
DLC configuration, LAN Manager 7-2

B
Bitronics interface AppleTalk 6-1 Boot Configuration Program B-13 Boot Prompt B-13 Bugs, reporting A-1

E
Ethernet, connecting to 2-3

F
Flash ROM updates Troubleshooting D-7 Flash ROM, reloading D-4 FTP, updating software D-2

C
Command syntax 3-2 Components, description of 2-1 Configuration Additional 11-1 AppleTalk 6-1 LAN Manager 7-1 LAT 8-1 NetWare 9-1 TCP/IP 10-1

H
Help, Reference Manual 1-2 HP host configuration 10-7

L
LAN Manager Windows NT DLC configuration 7-1, 7-2 NetBIOS configuration 7-6 Index-i

Index

L (cont.)
LAT DCPS printing software 8-4 Incoming logins 3-8 Outgoing sessions 4-2 PostScript printing 8-3 LPD host Troubleshooting B-3 LPR AIX configuration 10-5 Generic UNIX hosts 10-2 HP configuration 10-7 SCO UNIX configuration 10-9 Solaris configuration 10-11 ULTRIX configuration 10-11 Windows NT 10-12 LPR printing notes 10-4

P
Passwords Login 11-2 Privileged 11-1 Pinout information C-1 Port Access 11-6 Port parameters Parallel 11-5 Serial 11-4 PostScript configuration 11-3 PostScript Printing NetWare 9-7 Troubleshooting B-10 PostScript printing AppleTalk 6-3 LAT 8-3 TCP/IP 10-17 Printer Autosensing 11-3

N
NDS configuration using PCONSOLE

9-2
NetBIOS Configuration, LAN Manager 7-6 NetWare PostScript printing 9-7 QINST 9-5 Queue Password 9-7 Reloading software D-5 Troubleshooting B-6 Netware Binary printing 9-7

R
RTEL functionality 10-16

S
SCO UNIX configuration 10-9 Serial console port 3-8 Serial Information C-1 Service names, changing 5-2

Index-ii

Index

S (cont.)
Service parameters Banner 5-3 Binary 5-3 EOJ or SOJ string 5-2 Ident string 5-2 Ports 5-2 Rating 5-2 TCPPort 5-3 TelnetPort 5-3 Software, updating D-1 Solaris host configuration 10-11 Specifications Altitude E-1 Power E-1 Relative Humidity E-1 Temperature E-1 Support, technical A-1

NetWare B-6 PostScript B-10 Power-up B-1 Printing B-2 VMS B-4

U
ULTRIX host configuration 10-11 Updating software D-1

V
VMS Console connections 3-7 Troubleshooting B-4

W
Windows 95 LPR configuration 10-2 Windows NT configuration 10-12

T
TCP/IP Console Connections 3-5 PostScript Printing 10-17 Reloading software D-6 RTEL functionality 10-16 TCP socket connections 10-17 Technical support A-1 Telnet Outgoing sessions 4-1 Troubleshooting AppleTalk B-12 Flash ROM updates D-7 LPD B-3 Index-iii

Warranty Statement
Lantronix warrants for a period of FIVE YEARS from the date of shipment that each Lantronix ETS print server supplied shall be free from defects in material and workmanship. During this period, if the customer experiences difculties with a product and is unable to resolve the problem by phone with Lantronix Technical Support, a Return Material Authorization (RMA) will be issued. Following receipt of a RMA number, the customer is responsible for returning the product to Lantronix, freight prepaid. Lantronix, upon verication of warranty will, at its option, repair or replace the product in question, and return it to the customer freight prepaid. If the product is not under warranty, Lantronix will contact the customer who then has the option of having the unit repaired on a fee basis or having the unit returned. No services are handled at the customer's site under this warranty. Lantronix warrants software for a period of sixty (60) days from the date of shipment that each software package supplied shall be free from defects and shall operate according to Lantronix specications. Any software revisions required hereunder cover supply of distribution media only and do not cover, or include, any installation. The customer is responsible for return of media to Lantronix and Lantronix for freight associated with replacement media being returned to the customer. Lantronix shall have no obligation to make repairs or to cause replacement required through normal wear and tear of necessitated in whole or in part by catastrophe, fault or negligence of the user, improper or unauthorized use of the Product, or use of the Product in such a manner for which it was not designed, or by causes external to the Product, such as, but not limited to, power or failure of air conditioning. There are no understandings, agreements, representations or warranties, express or implied, including warranties of merchantability or tness for a particular purpose, other than those specically set out above or by any existing contract between the parties. Any such contract states the entire obligation of Lantronix. The contents of this document shall not become part of or modify any prior or existing agreement, commitment or relationship The information, recommendation, description and safety notations in this or other documents supplied by Lantronix are based on general industry experience and judgment with respect to such hardware and software. THIS INFORMATION SHOULD NOT BE CONSIDERED TO BE ALL INCLUSIVE OR COVERING ALL CONTINGENCIES. NO OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE OR MERCHANTABILITY, OR WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, ARE MADE REGARDING THE INFORMATION, RECOMMENDATIONS, DESCRIPTIONS AND SAFETY NOTATIONS CONTAINED HEREBY AND IN HARDWARE AND SOFTWARE SPECIFICATION DOCUMENTATION, OR INSTRUCTIONS SUPPLIED BY LANTRONIX. In no event will Lantronix be responsible to the user in contract, in tort (including negligence), strict liability or otherwise for any special, indirect, incidental or consequential damage or loss of equipment, plant or power system, cost of capital, loss of prots or revenues, cost of replacement power, additional expenses in the use of existing software, hardware, equipment or facilities, or claims against the user by its employees or customers resulting from the use of the information, recommendations, descriptions and safety notations supplied by Lantronix. Lantronix liability is limited (at its election) to (1) refund of buyer's purchase price for such affected products (without interest); (2) repair of such products, or (3) replacement of such products, provided however, that the buyer follows the procedures set forth herein Warranty claims must be received by Lantronix within the applicable warranty period. A replaced product, or part thereof, shall become the property of Lantronix and shall be returned to Lantronix at the Purchaser's expense. ALL RETURN MATERIAL MUST BE ACCOMPANIED BY A RETURN MATERIAL AUTHORIZATION NUMBER ASSIGNED BY LANTRONIX.

Warranty-1

Declaration of Conformity
(accordingly to ISO/IEC Guide 22 and EN 45014)
Manufacturers Name: Manufacturers Address: Lantronix 15353 Barranca Parkway Irvine, CA 92718

declares, that the product:


Product Name: Model Number(s): Terminal/Printer Server ETS4P4

conforms to the following Standards:


Safety: EMC: EN 60950:1988 + Amendments 1 and 2 Based upon EN 55022:1988 class A EN 50082-1:1992

Supplementary Information: The product complies with the requirements of the 89/336/EEC and 73/23/EEC declaratives.

Manufacturers Contract:

Director of Quality Assurance Lantronix 15353 Barranca Parkway Irvine, CA 92718 General Tel: 714/453-3990; Fax: 714/453-3995

The information in this guide may change without notice. The manufacturer assumes no responsibility for any errors which may appear in this guide. DEC, thickwire, thinwire, VMS, VT100, and ULTRIX are trademarks of Digital Equipment Corporation. UNIX is a registered trademark of AT&T. Ethernet is a trademark of XEROX. NetWare is a trademark of Novell Corp. AppleTalk, Chooser, and Macintosh are trademarks of Apple Computer Corp. Windows NT and Windows for Workgroups are trademarks of Microsoft Corporation. Portions copyright 1989,1991,1992,1993 Regents of the University of California. All rights reserved. Used with permission. Portions of this work are derived from the Standard C Library, copyright 1992 by P.J. Player, published by Prentice-Hall, and are used with permission. Copyright 1995, Lantronix. All rights reserved. No part of the contents of this book may be transmitted or reproduced in any form or by any means without the written permission of Lantronix. Printed in the United States of America. The revision date for this manual is February 13, 1997. Part Number: 900-056 Rev. A WARNING This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against such interference when operating in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with this guide, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause interference in which case the user, at his or her own expense, will be required to take whatever measures may be required to correct the interference. Warning: Changes or modifications to this device not explicitly approved by Lantronix will void the user's authority to operate this device. Cet appareil doit se soumettre avec la section 15 des statuts et rglements de FCC. Le fonctionnement est subject aux conditions suivantes: (1) Cet appareil ne doit pas causer une interfrence malfaisante. (2) Cet appareil dot accepter n'import quelle interfrence reue qui peut causer une opration indsirable.