Page 1
February 2004
LES2700A-16-R3
LES2700A-32-R3
Order toll-free in the U.S. 24 hours, 7 A.M. Monday to midnight Friday: 877-877-BBOX
FREE technical support, 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746
Mail order: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018
Web site: www.blackbox.com • E-mail: info@blackbox.com
CUSTOMER
SUPPORT
INFORMATION
16-Port Rackmount 10/100
and 32-Port Rackmount 10/100
Serial Terminal Servers
Installation Guide
Page 2
The information in this guide may change without notice. The manufacturer assumes no
responsibility for any errors which may appear in this guide.
DEC and LAT are trademarks of Digital Equipment Corporation. NetWare is a trademark
of Novell Corporation. UNIX is a registered trademark of The Open Group. Windows for
Workgroups, Windows 95, Windows 98, Windows 2000, and Windows NT are trademarks
of Microsoft Corporation.
Copyright 2004, Black Box Corporation. 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 Black Box Corporation. Printed in the United States of America.
The revision date for this manual is February 2004.
Part Number: 900-218
Rev.B
WARNING
This product has been designed 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.
Changes or modifications to this device not explicitly approved by Black Box Corporation
will void the user's authority to operate this device.
Cet appareil doit se soumettre avec la section 15 des statuts et règlements de FCC. Le
fonctionnement est subjecté aux conditions suivantes:
(1) Cet appareil ne doit pas causer une interférence malfaisante.
(2) Cet appareil doît accepter n'importé quelle interférence reìue qui peut causer une
opération indésirable.
Page 3
Introduction ................................................................................ 1
Supported Serial Protocols .......................................................................1
RS-232 .........................................................................................1
RS-423 .........................................................................................1
How to Use This Manual ..........................................................................2
Installation .................................................................................. 3
Terminal Server Product Descriptions .....................................................3
LES2700A-16-R3 Front Panel ....................................................3
LES2700A-32-R3 Front Panel ....................................................3
LEDs ............................................................................................4
Installing the Terminal Server ..................................................................5
Was the Installation Successful? ..............................................................6
Getting Started ........................................................................... 7
Configuration Methods .............................................................................7
EZWebCon ..................................................................................7
Using a Web Browser ..................................................................7
Incoming Logins ..........................................................................8
Console Terminal ........................................................................9
Services .....................................................................................................9
Using the Terminal Server ...................................................... 10
Console Server Example ........................................................................11
Define the Menus ......................................................................12
Enable Menu Mode ...................................................................13
Configure Switches ...................................................................14
Using Menus ..............................................................................15
Serial Tunnel Example ...........................................................................16
TCP Configuration ....................................................................16
UDP Configuration ....................................................................16
Multi-port Serial Tunnel Configuration ....................................17
Comm Port Redirector ............................................................................17
Enhanced Serial Support ........................................................................17
TCP/IP Configuration .............................................................. 20
Setting the IP Address ............................................................................20
Using EZWebCon .....................................................................20
Using a Directed Ping Packet ....................................................20
Using a BOOTP, DHCP, or RARP Reply .................................22
Page 4
Using the Command Line Interface ...........................................22
LPR Printing ...........................................................................................22
LPR on Windows NT 3.5.1 (and later) ......................................23
LPR on UNIX Hosts ..................................................................26
LPR on AIX Hosts .......................................................................7
LPR on HP Hosts .......................................................................28
LPR on SCO UNIX Hosts .........................................................29
RTEL Functionality ...................................................................30
Unix Host Troubleshooting ....................................................................30
NetWare Configuration ............................................................ 31
NDPS Printing ........................................................................................31
Configure your Terminal Server .............................................................31
NetWare Administrator Quick Setup Print Queues ................................32
PCONSOLE Print Queues ......................................................................33
NetWare Host Troubleshooting ..............................................................33
LAT Configuration ................................................................... 37
Printing Directly to a Port .......................................................................37
LAT Host Troubleshooting .....................................................................38
AppleTalk Configuration ......................................................... 39
Bitronics ..................................................................................................39
Macintosh Services .................................................................................39
AppleTalk Zones ....................................................................................39
AppleTalk Host Troubleshooting ...........................................................40
DLC Configuration for LAN Manager ..................................... 41
DLC Configuration .................................................................................41
Terminal Server Configuration ..................................................41
Host Configuration ....................................................................41
Contact Information ................................................................. 43
Problem Report Procedure ......................................................................43
Troubleshooting ....................................................................... 44
Power-up Troubleshooting .....................................................................45
DHCP Troubleshooting ..........................................................................47
BOOTP Troubleshooting ........................................................................47
RARP Troubleshooting ..........................................................................48
Modem Configuration Checklist ............................................................48
Entering Commands at the Boot Prompt ................................................49
Page 5
Pinouts ...................................................................................... 52
Ethernet Connector .................................................................................52
RJ45 Serial Connectors ..........................................................................52
RJ45 to DB25 ............................................................................53
RJ45 to DB9 ..............................................................................54
Updating Software 56
Choosing the Right Software File ..........................................................56
Obtaining Software .................................................................................56
Reloading Software ................................................................................56
Reloading Sequence ..................................................................57
Troubleshooting Flash ROM Updates ....................................................58
Specifications ........................................................................... 60
Power Information ..................................................................................60
Power Requirements ..................................................................60
Power Supply Cord ....................................................................60
Environmental Limitations .....................................................................60
Temperature ...............................................................................60
Altitude .....................................................................................60
Relative Humidity .....................................................................61
Frequently-used Commands .................................................. 62
Conventions ............................................................................................62
Server Commands ...................................................................................63
Port Commands ......................................................................................67
Protocol Commands ...............................................................................68
Declaration of Conformity ....................................................... 70
FCC Requirements for
Telephone-Line Equipment ..................................................... 71
Certification Notice for
Equipment Used in Canada .................................................... 72
Page 6
Federal Communications
Commission and Canadian
Department of
Communications Radio
Frequency Interface
Statements ................................................................................ 73
Normas Oficiales Mexicanas (NOM)
Electrical Safety Statement
Instrucciones de Seguridad .................................................... 74
Index .......................................................................................... 76
Page 7
1
1: Introduction
The Black Box LES2700A-16-R3 and LES2700A-32-R3 are Terminal Servers that
provide shared network access to terminals, devices, console ports, and printers for a
variety of network protocols and operating systems. These Terminal Servers support the
TCP/IP, IPX (NetWare), Local Area Transport (LAT), AppleTalk (EtherTalk), and
Microsoft LAN Manager protocols.
The Terminal Server stores its executable software in Flash (rewritable) ROM, meaning
that it does not have to download software from a host each time it boots. Software must
only be downloaded when a new software version becomes available. See Appendix 13
for more information.
1.1 Supported Serial Protocols
All Terminal Server models support the RS-232/423 serial protocol.
1.1.1 RS-232
The RS-232 line interface standard is a single-ended peer-to-peer interface. Today's
personal computers typically have at least one RS-232 serial port. It is the most common
serial protocol used today.
RS-232 is used for connecting devices across short distances at speeds up to 230.4 kb/s.
Faster speeds require shorter cabling to ensure error-free communication. The maximum
cable length at a given speed is determined by many factors, including the immediate
electrical environment and the quality of cable used, but is usually less than 15 meters at
high speeds.
1.1.2 RS-423
All of the Terminal Server models support the RS-423 line interface standard. RS-423
devices are interoperable with RS-232 devices. That is, RS-232 ports can receive data
reliably from RS-423 ports and vice-versa.
The main difference between RS-423 and RS-232 is that RS-423 employs lower voltage
signaling and differential receivers. RS-423 still uses single-ended transmitters for
compatibility with RS-232 receivers.
Page 8
2
1.2 How to Use This Manual
This guide is structured as follows:
Chapter 2, Installation explains how to physically install the Terminal Server.
Chapter 3, Getting Started explains the minimum configuration needed.
Chapter 4, Using the Terminal Server explains some of the ways that you can use
your Terminal Server.
Chapters 5 through 9 cover protocol-specific setup needed to install print queues and
otherwise use the Terminal Server.
Chapter 5, TCP/IP Configuration
Chapter 6, NetWare Configuration
Chapter 7, LAT Configuration
Chapter 8, AppleTalk Configuration
Chapter 9, DLC Configuration for LAN Manager
Appendices A through F provide supplementary information.
Appendix 10, Contact Information
Appendix 11, Troubleshooting
Appendix 12, Pinouts
Appendix 13, Updating Software
Appendix 14, Specifications
Appendix 15, Frequently-used Commands
Read chapters 2 through 4 in order, then proceed to the protocol-specific chapter that relates
to your network. Refer to Appendix 15 as needed. The Device Server Reference Manual,
located on the CD-ROM and web site, provides additional information about configuring
and using your Terminal Server.
Page 9
3
2: Installation
This chapter describes the various Terminal Server models and shows how to install them
into a basic network situation.
2.1 Terminal Server Product Descriptions
2.1.1 LES2700A-16-R3 Front Panel
The LES2700A-16-R3 has 16 RJ45 serial ports, a Reset button, an AUI Ethernet port, an
RJ45 Ethernet port for 10/100BASE-T, several LEDs, and a power switch.
Figure 2-1: LES2700A-16-R3 Front Panel
Note:
The first RJ45 port is also the serial console port; however, in most situations connecting a terminal to this port will not be necessary.
2.1.2 LES2700A-32-R3 Front Panel
The LES2700A-32-R3 has 32 RJ45 serial ports, a Reset button, an AUI Ethernet port, an
RJ45 Ethernet port for 10/100BASE-T, several LEDs, and a power switch.
Figure 2-2: LES2700A-32-R3 Front Panel
Note:
The first RJ45 port is also the serial console port; however, in most situations connecting a terminal to this port will not be necessary.
2
1
4
3
6
5
8
7
10
9
12
11
14
13
16
15
receive
transmit
reset
# aui
10/100
powerlink100okactivity
17
17-32
1-16
18
2
1
4
3
20
19
6
5
22
21
8
7
24
23
10
9
26
25
12
11
28
27
14
13
30
29
16
15
32
31
reset
# aui
10/100
powerlink100okactivity
Page 10
4
2.1.3 LEDs
Each Terminal Server has a total of 37 LEDs. Each serial port has one (LES2700A-32-R3)
or two (LES2700A-16-R3) corresponding LEDs that indicate receive and transmit activity,
and there are five LEDs on the right side of the case. Their functionality is shown in Table
2-1.
Table 2-1: Terminal Server Port LED Functionality
LED Function
activity Blinks to indicate Ethernet activity.
ok Blinks to indicate that the Terminal Server is functioning properly.
100 Lights to indicate a 100BASE-T rather than 10BASE-T Ethernet link.
link Lights to indicate a functional Ethernet network link.
power Lights to indicate the Terminal Server has power.
Page 11
5
2.2 Installing the Terminal Server
The following diagram shows a properly-installed LES2700A-16-R3. Installation will
generally be the same for both models, the only difference being the type of serial ports
available. See Terminal Server Product Descriptions on page 3 for more information.
Figure 2-3: Sample Network Layout (LES2700A-16-R3 shown)
To install the Terminal Server, complete the following steps in order.
1 Attach the two rack mount brackets to your Terminal Server and attach your brack-
eted Terminal Server to your rack. The brackets should go on both front corners or
both rear corners. (This is only necessary if you would like to mount the unit on a
rack.)
Figure 2-4: Rack Mount Bracket Installation
2 Connect one or more serial devices to the Terminal Server serial ports.
Console Terminal
Modem
10/100BASE-
T
Ethernet
Serial Printer
Terminal
LES2700A-16
2
3
4
5
-R3
-
Page 12
6
See Appendix 12, Pinouts, for information about what kinds of device attachments
the Terminal Server supports.
3 Connect an Ethernet cable to either the 10/100BASE-T port (shown) or a
transceiver connected to the AUI port.
The Terminal Server will boot without a valid Ethernet connection, but it will pause
to print a message asking if you want to stop at the Boot> prompt. If you do not respond to this message, it will wait for 10 seconds and then finish booting.
4 If desired, connect a terminal to the Terminal Server console port (port 1). This will
enable you to receive diagnostic and initial configuration messages.
Note: The default serial port settings are 9600 baud, 8 bit characters, and no
parity.
5 Attach one end of the power cable to the Terminal Server and plug the other end into
an electrical outlet.
6 Flip the power switch to the ON position. The Terminal Server will go through two
steps to begin normal operation:
A It runs through a set of power-up diagnostics for approximately 12 seconds. The
LEDs show varying patterns corresponding to the tests being run.
B It tries to obtain TCP/IP configuration information via DHCP, BOOTP, and
RARP. This may take as long as 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.
7 Install EZWebCon on your 32-bit Windows PC, Apple Macintosh, or Solaris com-
puter. The EZWebCon software is located on the distribution CD-ROM.
2.3 Was the Installation Successful?
If the Terminal Server appears to be working and the unit is connected to the network, there
are a couple of ways to confirm that the unit is visible to network hosts:
If the Terminal Server has an IP address, ping it from a TCP/IP host.
If the Terminal Server has an IP address, use EZWebCon to log into it.
If the Terminal Server does not have an IP address, assign one by following the in-
structions in Section 5.1 on page 20.
When you are satisfied that the Terminal Server is working properly, proceed to Chapter 3,
Getting Started. If the Terminal Server does not boot properly, see Appendix 11,
Troubleshooting.
Page 13
7
3: Getting Started
It is important to consider the following points before logging into and configuring the
Terminal Server:
You must configure the Terminal Server IP address before any TCP/IP functionality
is available. (See Setting the IP Address on page 20) You cannot use the ThinWeb
Manager until you have configured an IP address.
Changing any server, service, or port setting requires privileged user status. The de-
fault privileged password is system.
The login password is required for remote console logins. The default login pass-
word is access.
Note: If you would like to change either the privileged or login password, ei-
ther use EZWebCon or refer to the Device Server Reference Manual
located on the CD-ROM.
3.1 Configuration Methods
3.1.1 EZWebCon
The EZWebCon configuration software is the recommended way to configure the Terminal
Server. EZWebCon’s graphical user interface guides first time users through the initial
configuration process and allows experienced users to update any configurable parameters.
EZWebCon requires a Java Virtual Machine (JVM) on the client. Black Box provides JVM
installers for Solaris and 32-bit Windows users, as well as source code and instructions for
compiling it for other systems.
The EZWebCon software is located on the distribution CD-ROM. All instructions for
installing EZWebCon are provided in the README file. For assistance once EZWebCon
is running, refer to the EZWebCon on-line help.
Note: See Appendix 13 for more information.
3.1.2 Using a Web Browser
The Web Manager web browser interface allows you to log into and configure your
Terminal Server using a standard web browser with JavaScript enabled. Simply type the
Terminal Server IP address or resolvable text name into the browser’s URL/Location field.
Page 14
8
Figure 3-1: Sample Web Browser Login
Once you have connected to the Terminal Server, you will see the Black Box ThinWeb
Manager interface. Use the left-hand menu to navigate to subpages where you can
configure important settings as well as view statistics and other server information.
Figure 3-2: Web Manager Interface
3.1.2.1 Disabling the Web Server and FTP Server
Disable the web server using the following command:
DEFINE PROTOCOL HTTP [ENABLED|DISABLED]
Disable the FTP server using the following command:
DEFINE PROTOCOL HTTP [ENABLED|DISABLED]
3.1.3 Incoming Logins
Incoming logins made via EZWebCon can be used to configure the Terminal Server.
Incoming LAT and TCP/IP logins can also be used.
Incoming Telnet is only possible if your Terminal Server has an IP address configured.
Incoming Telnet is enabled by default to allow TCP/IP connections. To change this setting,
use the Define Server Incoming command described in the Command Reference chapter
of the Device Server Reference Manual located on the CD-ROM.
Page 15
9
Incoming logins do not prompt for a login password, so you may wish to disable them for
security reasons. If it is undesirable to disable incoming logins, the Terminal Server can be
configured to prompt for a password with the Define Server Incoming Password Enabled
command.
3.1.4 Console Terminal
To configure the Terminal Server via a console terminal, attach a terminal to the serial
console port (port 1) and press the Return key. You will see a Local> prompt at which you
can enter configuration commands.
3.2 Services
With few exceptions, you must create a service before you can configure print queues on
the Terminal Server. A service is a resource accessible to network hosts. A Black Box
service is also known as a remote printer name or remote queue name on many operating
systems.
Page 16
10
4: Using the Terminal Server
The sections in this chapter show how to use the Terminal Server in a variety of
applications.
For detailed instructions on how to set up the Terminal Server as a console server,
see Console Server Example on page 11.
For instructions on how to use the Terminal Server in serial tunnel mode, see Serial
Tunnel Example on page 16.
For information about using the Terminal Server with the Black Box Comm Port Re-
director, see Comm Port Redirector on page 17.
Keep in mind that you must reboot the Terminal Server after issuing a Define command.
The command will take effect when the Terminal Server reboots. The one exception is that
Define Port commands take effect when a port is logged out.
Page 17
11
4.1 Console Server Example
When you use the Terminal Server as a console server, you can remotely manage devices
and equipment from anywhere on the network.
Figure 4-1: Console Server
To use the Terminal Server as a console server, you must connect the Terminal Server serial
ports to the serial console/management ports of other equipment such as UNIX servers,
PBX switches, routers, network switches, or other similar devices.
Once you have completed the connections, you can establish a Telnet connection to the
Terminal Server IP address and socket number of the desired port. The Terminal Server
serial ports allow two types of socket connections: Telnet IAC interpretation at socket
200x, and raw TCP connections at socket 300x, where x is the port number. For example,
to open a Telnet connection to port 4 of an Terminal Server at IP address 192.0.1.168, you
would issue the command “Telnet 192.0.1.168:2004” from your system prompt.
In addition to direct Telnet connections, you can use the Terminal Server’s built-in menu
feature. The Terminal Server menu allows you to connect to the IP address of the Terminal
Server and be greeted with a menu with which to connect to each attached serial device.
Menu choices are an easy way to let users access often-used hosts and services without
needing to know any Terminal Server command syntax, the IP addresses of the non-local
devices, or the socket numbers involved.
Page 18
12
Figure 4-2: Sample Menu
4.1.1 Define the Menus
You create menus with the Set/Define Menu command. Each menu entry is numbered.
Each command includes a name for the menu item and a command that is executed on the
Terminal Server when that menu item is chosen. Users type the number of the command
they wish to execute and press Return.
To give your menu a name, use a Define Menu Title command.
Figure 4-3: Menu Title
There are three types of menu entries: those that connect users to devices on the network,
those that connect users to devices attached to the Terminal Server, and those that function
locally on the Terminal Server. The basic syntax of the Define Menu command includes a
menu item number, a menu item name, and a command that is executed when the user
chooses that menu item.
Figure 4-4: Generic Menu Command
Note:
You must enclose both the menu item and the command in their own
sets of quotation marks.
To allow users to connect to a device on the network from a terminal connected to the
Terminal Server, use a Telnet command.
Figure 4-5: Menu Entries for Network Connections
Black Box Console Server
1) Cisco Router
2) Sun Server
3) HPUX Server
4) Linux Server
Enter Selection:
5) PBX Switch
6) Terminal Server Prompt
7) Logout
8)
Local>> DEFINE MENU TITLE "Black Box Console Server:"
Local>> DEFINE MENU n "Name" "command"
Local>> DEFINE MENU 1 "Cisco Router" "telnet 192.0.1.250;kill"
Local>> DEFINE MENU 2 "Sun Server" "telnet 192.0.1.251;kill"
Page 19
13
To allow users to connect from the network to a device connected to the Terminal Server
(or from one Terminal Server port to another) add a Connect Local command.
Figure 4-6: Menu Entries for Local Connections
To allow users to access a local service on the Terminal Server, add a general Terminal
Server command.
Figure 4-7: Menu Entries for Manipulating the Terminal Server
Note: The Exit command only works in menu mode. It allows users to return
to the Local> prompt on the Terminal Server on which the menu was
configured. It is helpful to include this command in your menus until
you have fully tested them - otherwise there is no way for users on
menu mode ports to return to the Local> prompt.
To review the menu you’ve just created, type Show Menu at the Local> prompt. The menu
created by the previous commands would look like this:
Figure 4-8: New Menu
4.1.2 Enable Menu Mode
You must enable menu mode for all ports on which you wish the menu system to work.
Ports 2-4 will be used for the examples in this section.
Figure 4-9: Enabling Menu Mode
Local>> DEFINE MENU 3 "HPUX Server" "connect local port_3"
Local>> DEFINE MENU 4 "Linux Server" "connect local port_4"
Local>> DEFINE MENU 5 "PBX Switch" "connect local port_5"
Local>> DEFINE MENU 6 "Terminal Server Prompt" "exit"
Local>> DEFINE MENU 7 "Logout" "logout"
Local_1>> show menu
Title for the menu is "Black Box Console Server"
1: Cisco Router --> "telnet 192.0.1.250;kill"
2: Sun Server --> "telnet 192.0.1.251;kill"
3: HPUX Server --> "connect local port_3"
4: Linux Server --> "connect local port_4"
5: PBX Switch --> "connect local port_5"
6: Terminal Server Prompt --> "exit"
7: Logout --> "logout"
Local>> DEFINE PORT 2-4 MENU ENABLED
Local>> LOGOUT PORT 2-4
Page 20
14
If you want incoming logins from the network to be able to use the menu, you must enable
menu mode on port 0. Users who Telnet into the Terminal Server would see the menu
rather than the Local> prompt.
Note: Administrators can bypass the menu and get to the Terminal Server
command line by forming a Telnet connection to port 7000.
4.1.3 Configure Switches
Switches allow users to move around within open sessions and return to the Terminal
Server Local> prompt if needed. It is important to set switches if you intend to allow serial
port users to hold multiple sessions to remote servers. You must set switches for all of the
ports for which menu mode was enabled in Section 4.1.2.
Any key may be used for a switch, provided that the chosen keys do not interfere with the
sessions. To use a control key, type a carat (^).
Figure 4-10: Configuring Switches
Note: Define Port Break Local allows the Terminal Server to recognize the
switches you just configured.
To check switch configurations, enter the Show/List Port command and specify the ports
that are used for menu mode.
Figure 4-11: Show Port Screen
Local>> DEFINE PORT 2-4 LOCAL SWITCH ^X
Local>> DEFINE PORT 2-4 FORWARD SWITCH ^F
Local>> DEFINE PORT 2-4 BACKWARD SWITCH ^B
Local>> DEFINE PORT 2-4 BREAK LOCAL
Page 21
15
4.1.4 Using Menus
When you log into a port with menu mode enabled, you will be presented with an initial
login screen.
Figure 4-12: Login Screen
1 Enter your user name (in this case, Bob) and press Return.
Figure 4-13: Login Screen, part 2
2 As instructed, press the Return key once more to see the actual menu.
Figure 4-14: Login Menu
3 Choose a menu option. Type the number of the desired option and press Return. For
example, to connect to the Linux server, you would press 2 and then press Return.
4 To return to the menu from your Linux session, press the configured Local Switch
key. In this case, the Local Switch is Ctrl-X (see Figure 4-10).
Note: Switch keys only work within sessions. They do not work from the menu
screen - you must enter a menu number to go to a session from the
menu screen.
Black Box LESxx Version B3.6/3 (000410)
Type HELP at the 'Local_10> ' prompt for assistance.
Username>
Username> Bob
Press <CR> to continue...
Black Box Console Server
1) Cisco Router
2) Sun Server
3) HPUX Server
4) Linux Server
Enter Selection:
5) PBX Switch
6) Terminal Server Prompt
7) Logout
8)
Page 22
16
4.2 Serial Tunnel Example
Two Terminal Servers can be connected to emulate a direct serial connection across a LAN
or WAN. Servers connected in this way can pass data only—they will not be able to pass
status signals (DSR/DTR, CTS/RTS, etc.) or preserve timing between characters. The basic
network configuration for this virtual serial line is shown in Figure 4-15.
Figure 4-15: Back-to-Back Terminal Server Connections
4.2.1 TCP Configuration
Assuming the Terminal Server serial port parameters have been configured properly, the
Terminal Servers would be configured as follows.
LES_A
Local>> DEFINE PORT 2 DEDICATED TELNET 192.168.5.10:3001T
Local>> DEFINE PORT 2 AUTOSTART ENABLED
LES_B Local>> DEFINE PORT 3 ACCESS REMOTE
Local>> DEFINE PORT 3 DEDICATED NONE
Local>> DEFINE PORT 3 AUTOSTART DISABLED
Note: If the Terminal Servers are on different IP subnets, configure the de-
fault gateway on each unit with the Change Gateway command.
The above commands create a raw (8-bit clean) TCP connection between LES_A port 2
and LES_B port 3 once the units have been power-cycled. The commands for LES_A
ensure that it will automatically connect to LES_B each time it is booted. The commands
for LES_B ensure that it is always available to accept connections from LES_A.
Note: You must log out the Terminal Server ports after configuring them so
that the commands can take effect.
4.2.2 UDP Configuration
When the UDP protocol is used, there is no connection; each Terminal Server must be told
explicitly which hosts it is allowed to accept packets from. Each Terminal Server would
have to be configured to both send packets to and accept packets from the other Terminal
Server.
Serial Device
Serial Device
LES_B
LES_A
Ethernet
Ethernet
LAN/
WAN
Page 23
17
LES_A Local>> DEFINE PORT 2 DEDICATED TELNET 192.168.5.10:4096U
Local>> DEFINE PORT 2 AUTOSTART ENABLED
Local>> DEFINE PORT 2 ACCESS DYNAMIC
LES_B Local>> DEFINE PORT 3 DEDICATED TELNET 192.168.5.2:4096U
Local>> DEFINE PORT 3 AUTOSTART ENABLED
Local>> DEFINE PORT 3 ACCESS DYNAMIC
Setting up Dedicated hosts ensures that the units will always talk to each other. Enabling
Autostart for both units enables one Terminal Server to send data to the other Terminal
Server without having to wait for a serial carriage return to start the session. LES_B knows
exactly which other Terminal Server to accept connections from. Finally, when Autostart
is enabled, the access mode must be either Local or Dynamic (Dynamic is more flexible).
4.2.3 Multi-port Serial Tunnel Configuration
You can create serial tunnels for any available ports on the Terminal Server. Each serial
tunnel must point from one Terminal Server port to one different serial device port (such
as a serial port on a Terminal Server or MSS server).
4.3 Comm Port Redirector
The Black Box Comm Port Redirector application allows PCs to share modems and other
serial devices connected to the Terminal Server using Microsoft Windows or DOS
communication applications. The Redirector intercepts communications to specified
Comm ports and sends them over an IP network connection to the Terminal Server serial
port. This enables the PC to use the Terminal Server serial port as if it were one of the PC
Comm ports. Using their existing communications software, PC users dial out to a remote
host through a modem connected to the Terminal Server.
The Comm Port Redirector software and installation instructions are included on the
distribution CD-ROM and web site.
4.4 Enhanced Serial Support
Enhanced serial handling support has been added to the Terminal Server product line.
These new features allow much more control of how a server will bundle received serial
characters into network packets. Several new commands have been added to configure this
functionality.
To start a connection, the autostart functionality has been enhanced to allow sessions to be
initiated by a sequence of 1 or 2 characters. Either of the characters can be a wildcard,
signified by the ANY keyword.
DEF PORT n AUTOSTART CHAR ["x" | ANY | NONE] ["x" | ANY]
In addition, the characters that start the connection can either be passed to the host as the
first bytes of data or can be discarded.
DEF PORT n AUTOSTART SAVE [1 | 2 | NONE]
Page 24
18
where "x" is any valid character. Non-printable characters can be specified as "\xx" where
xx is the hex value of the character wanted. Note that data can only be saved if the port is
set to dedicated mode. In all other modes autostart chars are discarded.
Once the connection has been started, several different triggers can be used to force the
server to transmit all accumulated serial data to the host. These triggers are individually
described below.
The first trigger will allow serial data to be accumulated until a "timeout" condition has
been detected. This timeout may be either a period of time since the last character was
received or the time since the current "character burst" was started. The command syntax is:
DEF PORT n DATASEND TIMEOUT [IDLE | FRAME] [n | NONE]
Several simple examples should help illustrate how this trigger works. For example the
command "DEFINE PORT 2 DATASEND TIMEOUT IDLE 50" would look like:
xx x (data) x xx x x xxx xx xx
|----------------------|
50 milliseconds transmit packet
Using the command like "DEF PORT 2 DATASEND TIMEOUT FRAME 150" would
result in the following behavior.
x x x xxx xx (data) x x xx xxxxxxxx xx xxxx xx xxxx
|-------------------------------------------------------------------|
150 milliseconds transmit packet.
The second trigger can be used to specify a one or two byte character sequence that will cause the accumulated serial data to be transmitted.
The command syntax is:
DEF PORT n DATASEND CHAR [x1 | ANY | NONE] [x2 | ANY]
Again, examples may help explain how these commands work. The command "DEFINE
PORT 2 DATASEND CHAR Z" would transmit any accumulated data as soon as the "Z"
character is detected in the data stream.
x x x xxx xx x (data) x x xx x x xxxxxxx x Z
|----------------------------------------------------------------|
transmit packet
Page 25
19
The command "DEFINE PORT 2 DATASEND CHAR Z &" would send any accumulated
data as soon as the characters "Z&" are detected in the data stream.
x x x xxx xx x (data) x x xx x Z xxxxx x Z &
|---------------------------------------------------------------|
transmit packet
The DATASEND match characters can either be sent to the host as part of the data or can
be discarded. Use the command:
DEF PORT n DATASEND SAVE [1 | 2 | NONE]
There are several important caveats in this functionality:
The timer resolution on these products is approximately 20 milliseconds. Any time-
out values lower than 30 msec will be approximated as well as possible.
Packets created by the serial handling rules will be queued to the Ethernet driver as
a single operation, but there is no guarantee that they will be received at the network
host in a single network read.
If the serial input buffer is filled, the accumulated data will be queued to the Ethernet
driver regardless of the serial handling rules. The serial input buffer size is 1024
bytes.
Page 26
20
5: TCP/IP Configuration
The EZWebCon configuration software is the easiest way to configure the Terminal Server.
The following sections cover IP address configuration and print configuration methods for
TCP/IP hosts.
5.1 Setting the IP Address
The Terminal Server IP address must be configured before any TCP/IP functionality is
available. Use one of the following methods to set the IP address: EZWebCon; a directed
Ping packet; a BOOTP, DHCP, or RARP reply; or commands entered via the command
line interface.
5.1.1 Using EZWebCon
Use the following steps to assign an IP address using the EZWebCon Expert Shell.
1 From the Action menu, select Assign IP Address.
2 Enter or change the IP-related settings:
A For Ethernet Address, enter the number that appears on the bottom label of
your Terminal Server.
B For IP Address, enter the desired IP address to use for this Terminal Server.
C For Subnet Mask, change the values provided only if you wish to use a mask
other than the default. The default value should be correct in most cases.
D For Loadhost, enter the IP address of the loadhost where you intend to store
your operating code.
3 Click OK.
4 Reboot the Terminal Server. EZWebCon will let you know whether the configura-
tion was successful.
Note: If you have an older version of EZWebCon, refer to the Readme that
was included with it.
5.1.2 Using a Directed Ping Packet
The ARP/ping method is available under UNIX and Windows-based systems. If the
Terminal Server has no IP address, it will set its address from the first directed IP packet it
receives.
Page 27
21
On a UNIX host, create an entry in the host’s ARP table and substitute the intended IP
address and the hardware address of the Terminal Server, then ping the Terminal Server.
This process typically requires superuser privileges.
Figure 5-1: ARP and Ping on UNIX
In order for the ARP command to work on Windows, the ARP table on the PC must have
at least one IP address defined other than its own. If the ARP table is empty, the command
will return an error message. Type ARP -A at the DOS command prompt to verify that there
is at least one entry in the ARP table.
Figure 5-2: ARP and Ping on Windows
Note:
There should be replies from the IP address if the ARP command
worked.
When the Terminal Server receives the ping packet, it will notice that its IP address is not
set and will send out broadcasts to see if another node is using the specified address. If no
duplicate is found, the Terminal Server will use the IP address and will respond to the ping
packet.
The Terminal Server will not save the learned IP address permanently; this procedure is
intended as a temporary measure to enable EZWebCon to communicate with the Terminal
Server, or allow an administrator to Telnet into the Terminal Server. Once logged in, the
administrator can enter the Change IPaddress command to make the address permanent.
Figure 5-3: Configuring Permanent IP Address
Any host wishing to access the Terminal Server will have to be told the Terminal Server’s
IP address. This is typically configured in the unix file /etc/hosts or via a nameserver. Refer
to the host’s documentation for additional information.
# arp -s 192.0.1.228 00:80:a3:xx:xx:xx
% ping 192.0.1.228
C:\ ARP -S 192.0.1.228 00-80-A3-XX-XX-XX
C:\ PING 192.0.1.228
% telnet 192.0.1.228
Trying 192.0.1.228
Black Box LESx Version n.n/n (yymmdd)
Type Help at the ‘Local_>’ prompt for assistance.
Enter Username> gopher
Local> SET PRIVILEGED
Password> system (not echoed)
Local>> DEFINE IPADDRESS 192.0.1.228
Page 28
22
5.1.3 Using a BOOTP, DHCP, or RARP Reply
At boot time a host-based DHCP, BOOTP, or RARP server can respond to a Terminal
Server request for an available IP address. For information about configuring the DHCP,
BOOTP, or RARP server, see your host documentation.
5.1.4 Using the Command Line Interface
1 Connect to the serial port (Port_1) using a console terminal or a terminal emulation
program, and press Return. The serial port settings are 9600 baud, 8 bits, 1 stop bit,
no parity.
2 Become the privileged user.
Figure 5-4: Becoming the Privileged User
3 Enter the new IP address.
Figure 5-5: Configuring the IP Address
5.2 LPR Printing
The Terminal Server provides two major methods of printing via TCP/IP: Berkeley remote
LPR and RTEL host software.
Two parameters must be configured for LPR printing:
1 The IP address or host name of the Terminal Server.
2 The remote output queue (the name of the service on the Terminal Server).
In addition, there are a few important things to note about LPR printing:
Windows for Workgroups, Windows 95, and Windows 98 do not support LPR di-
rectly; however, Black Box has provided a peer-to-peer printing solution on the distribution CD-ROM.
Local> SET PRIVILEGED
Password> system (not echoed)
Local>>
Local>> define server ipaddress 192.0.1.201
Page 29
23
Because of the way the LPR protocol is typically implemented on the host, the pro-
cessing options and banner page are sent after the job data itself. The Terminal Server 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. If banners are not needed, they can be disabled.
The Terminal Server cannot print multiple copies of the print job when using the
“-#n” lpr option.
If two print queues on the host refer to two services on the same Terminal Server,
they must use separate spooling directories.
No special purpose input or output filters can be used when printing via LPR. If this
functionality is necessary, use the named pipe interface program in the RTEL print
queue configuration software.
5.2.1 LPR on Windows NT 3.5.1 (and later)
This section assumes that TCP/IP, Simple TCP/IP, and Microsoft TCP/IP printing have
been installed on the Windows NT host.
1 In the Control Panel, double-click the Printers icon.
2 Double-click the Add Printer icon.
3 In the window that appears, choose My computer and click Next.
Page 30
24
4 Select the Add Port button and click Next.
5 Select LPR Port.
Note: If LPR Port is not an option, open the Network Control Panel and add
“Microsoft TCP/IP Printing” to the List of services.
6 Enter the name or IP address of your Terminal Server on the first line, and enter the
name of your Terminal Server print service on the second line.
Page 31
25
7 Select the manufacturer and printer type.
8 Enter the queue name.
9 If applicable, choose Shared and select the type of operating system that the printer
will be working with. (First confirm that the print queue is working.)
Page 32
26
10 Test the printer by choosing Yes and clicking Finish.
5.2.2 LPR on UNIX Hosts
The Berkeley remote printing system is supported on many machines, and is simple to
configure. This section describes how to configure LPR print queues on generic UNIX
hosts such as SUN hosts. There are slight variations in LPR configuration for AIX, HP, and
SCO hosts, as will be explained in the following sections.
1 Install a print queue on your host by adding the Terminal Server name and IP address
to the /etc/hosts file:
Figure 5-6: Adding /etc/hosts Entry
2 Add the host print queue to the /etc/printcap file. The punctuation shown in Figure
5-7 is required, and no extra spaces should be added.
Figure 5-7: Adding /etc/printcap Entry
This will create a host queue named les_prt. The rm parameter is the name of the
Terminal Server in the host's address file, the rp parameter is the name of the service
as it exists on the Terminal Server, and the sd parameter specifies the name of a directory used to hold temporary spooling files.
xxx.xxx.xxx.xxx LES_xxxxxx
les_prt|Printer on LAB LES:\
:rm=LES_xxxxxx:\
:rp=LES_xxxxxx_TEXT:\
:sd=/usr/spool/lpd/les_prt:
Page 33
27
3 Create a world-writable spooling directory using the mkdir command.
Figure 5-8: Creating Spooling Directory
4 If desired, use the mx option to allow unlimited size files to be printed and the sh
option to prevent header pages from being generated. See the host's documentation
or man pages for more information on the format of the printcap file and how to create the spool directory.
5 Print to the queue using normal lpr commands:
Figure 5-9: Printing to Queue
5.2.3 LPR on AIX Hosts
The System Management Interface Tool (SMIT) allows you to enable LPD printing and
create print queues. LPR has only been tested on AIX versions 3.2 and higher.
To create a print queue:
1 At the host prompt, type smit.
2 Choose Print Spooling.
3 Choose Manage Print Server and Start the Print Server Subsystem (lpd dae-
mon).
4 In the Start the Print Server Subsystem dialog box, type both in the first field.
5 The message “The lpd subsystem has been started” will appear. Click Done.
To add a print queue:
1 From the main window, choose Print Spooling.
2 Choose Manage Print Server and Manage Print Queues.
3 Choose Add a print queue.
# mkdir /usr/spool/lpd/les_prt
# chmod 777 /usr/spool/lpd/les_prt
% lpr -Ples_prt /etc/hosts
Page 34
28
4 From the dialog box that appears, choose remote.
5 From the next dialog box, choose Remote Printing.
6 The Add a Standard Remote Print Queue dialog box will appear. Enter the fol-
lowing information.
The name of the print queue,
The name of the Terminal Server unit,
The name of the Terminal Server service,
The type of print spooler on the remote server, and
A description of the printer on the remote server.
7 A dialog box will appear: “Added print queue les_prt”. Click Done.
Note: If you are unable to use SMIT, see the Device Server Reference Man-
ual on the CD-ROM for UNIX commands used to set up print queues.
8 Print to the queue using normal lp syntax.
Figure 5-10: Printing to Queue
5.2.4 LPR on HP Hosts
The System Administration Manager (SAM) allows you to create print queues.
Note: If you are unable to use SAM, the Device Server Reference Manual lo-
cated on the CD-ROM describes UNIX commands that can be used to
set up print queues.
To create a print queue:
1 At the HP prompt, type sam.
2 From the main application window, choose Printers and Plotters.
3 In the Printers and Plotters window, choose Printers/Plotters.
4 In the pull-down menu, select Remote Printer/Plotter from the Actions menu.
5 The Add Remote Printer window will appear. SAM will prompt you for:
The printer name (the name of the print queue),
% lp -dles_prt filename
Page 35
29
The remote system name (the Terminal Server name),
The remote printer name (the Terminal Server service),
The remote cancel model, and
The remote status model.
5.2.5 LPR on SCO UNIX Hosts
LPR is supported in SCO V3.2 release 4 with TCP/IP Version 1.2 and greater.
To configure a print queue using LPR, issue the mkdev rlp command. This will install the
Berkeley remote printing files and executable programs.
Note: The mkdev rlp command should only be issued once, or serious prob-
lems will occur. If this happens, contact SCO technical support.
You can print to this queue using normal lp syntax once the remote printer is set up. To
create a remote printer:
1 Issue the rlpconf command.
2 Answer the questions that follow.
Figure 5-11: Configuring Remote Printer
In the example, the printer name is your Terminal Server service name, and the remote host name is the name of your Terminal Server as it is listed in your hosts file.
During initial configuration, the queue name must be the same as the remote printer name.
However, you may change the queue name later by manually editing the printcap file.
Remote Printing Configuration
Enter information for remote printers or local printers accepting remote printing requests
Please enter the printer name (q to quit): backupprinter
Is printer backupprinter a remote printer or a local printer? (r/l) r
Please enter the name of the remote host that backupprinter is attached to: LES_xxxxxx
The backupprinter is connected to host LES_xxxxxx.
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 LES_PRT’s /etc/hosts.equivor or /etc/hosts:lpd file.
Make sure backupprinter appears in /etc/printcap (in BSD format).
Make sure backupprinter has a spool directory on LES_PRT.
Putting the printer in printer description file and creating spool directory... done
Updating LP information... done
Page 36
30
5.2.6 RTEL Functionality
If the LPR method of printing is not adequate for an application (for example, if you need
banners before jobs, or more flexibility), configure the Black Box-supplied RTEL software
on the host. After installing the software configuring the connections to the Terminal
Server, you can use normal UNIX print commands and queue utilities such as lpc and
lpstat.
Note: RTEL binaries are provided for many systems. Source code is also
provided for use on non-supported systems.
To print to the Terminal Server using special formatting or using third-party software
packages, you may have to create print pipes on the host. The RTEL software provides
this functionality by providing a UNIX named-pipe interface.
To recreate the RTEL source files:
1 Copy the file RTEL_SRC.TAR in binary mode from the distribution CD-ROM to
the UNIX host.
2 Untar the archive.
3 See the README files in the created directories that describe the contents of the
RTEL distribution and man pages that describe the actual software functionality.
5.3 Unix Host Troubleshooting
Table 5-1: TCP Troubleshooting
Area to Check Explanation
The Terminal Server IP address and
name are entered in the host file
Telnet to the Terminal Server using the name in the
host file and verify that the Terminal Server name is
resolvable and that the Terminal Server is reachable
via the network.
Jobs that appear in the host queue
reach the Terminal Server
From within the LPC administrative utility, enter these
commands to clear and reset the host queue:
abort queue
clear queue
enable queue
start queue
Page 37
31
6: NetWare Configuration
The EZWebCon configuration software is the easiest way to configure the Terminal Server.
The following sections cover print configuration methods for NetWare hosts.
Note: The Terminal Server needs an IP address before you can use EZWeb-
Con. See Setting the IP Address on page 20 for instructions.
This chapter explains creating NDS print queues with NetWare Administrator and with the
PCONSOLE Quick Setup option. To create NDS print queues, you must be running
NetWare version 4.x with NDS capabilities.
If you are running NetWare versions 2.x, 3.x, or version 4.x with bindery emulation, you
may configure bindery print queues using QINST (bindery only) or PCONSOLE. For more
information, see the NetWare chapter of the Device Server Reference Manual located on
the CD-ROM.
6.1 NDPS Printing
For instructions on setting up NDPS, refer to your Novell Documentation.
6.2 Configure your Terminal Server
1 License NDS on your Terminal Server using the string obtained from Black Box.
Figure 6-1: Licensing NDS
2 Define the directory service tree in which the Terminal Server is located.
Figure 6-2: Defining Directory Service Tree
Note:
For an explanation of the structure of the NetWare Directory Service
tree, see your host documentation.
3 Define the directory service context in which the Terminal Server is located.
Figure 6-3: Defining Directory Service Context
Local>> DEFINE PROTOCOL NETWARE DSLICENSE licensestring
Local>> DEFINE PROTOCOL NETWARE DSTREE foodco
Local>> DEFINE PROTOCOL NETWARE DSCONTEXT ou=kiwi.ou=exotic.o=fruit
Page 38
32
4 Enter the List Protocol NetWare Access command to ensure that at least one of the
file servers in the directory service tree is in the access list.
5 If desired file server is not in the access list, add it.
Figure 6-4: Defining Access List
6 Reboot the Terminal Server.
Figure 6-5: Rebooting
6.3 NetWare Administrator Quick Setup
Print Queues
The NetWare Administrator management utility allows you to manage network resources,
such as queue-based print services, in a tree structure. You can either use the Quick Setup
option or individually create printing-related objects.
Note: NetWare Administrator can be used for both NDS and bindery print
queues.
To create a print queue with the Quick Setup option:
1 Start the NetWare Administrator.
2 In the Directory Tree windows, select the context in which to install the printer.
3 From the Menu Bar, select Tools: Print Services Quick Setup.
4 In the Print Server Name field, enter the name of your Terminal Server (viewable
by entering the Show Server command at the Local> prompt).
5 In the Printer Name field, enter the name of the desired print service configured on
your Terminal Server. For example, LES_xxxxxx.
6 In the Print Queue Name field, enter the name of the print queue to create. The
name should be meaningful to you; it will not affect Terminal Server configuration.
7 Click Create.
8 Reboot the Terminal Server.
Local>> DEFINE PROTOCOL NETWARE ACCESS fileserver
Local>> INITIALIZE DELAY 0
Page 39
33
6.4 PCONSOLE Print Queues
1 Log in as Admin on the file server you will be changing.
2 At the prompt, type PCONSOLE to start the utility.
For example, if your file server is mapped to the F: drive, you would use the F:
prompt.
3 From the main menu, choose Quick Set-Up.
4 When prompted by PCONSOLE, enter the information with which to configure the
print queue.
The print server name (LES_xxxxxx),
The new printer name (service name, such as LES_xxxxxx),
The new print queue name, and
The print queue volume (the name of the file server from which the printer re-
ceives print requests).
The remaining fields can be left in their default settings.
5 Press the F10 key to save the print queue information.
6 Reboot the Terminal Server.
6.5 NetWare Host Troubleshooting
Table 6-1: NetWare Host Troubleshooting (Bindery Mode)
Area to Check Explanation
The print server names in PCONSOLE match the Terminal Server
name and its service name
Use PCONSOLE to check.
The Terminal Server NetWare access
table
Use the Show Protocols NetWare Access command.
Scanning too many file servers can cause a delay
between jobs. Configure the access list to only scan for
jobs on the file servers of interest.
Page 40
34
Table 6-2: NetWare Host Troubleshooting (NDS)
Area to Check Explanation
The Terminal Server NetWare access
table
Use the Show Protocols NetWare Access command. By
default, only local file servers are scanned for queues.
The Terminal Server login password
and the queue password on the file
server
The passwords must match or the Terminal Server will
not be able to log into the file servers to scan for jobs.
The Terminal Server has successfully
attached to the queue
Type NETSTAT at the Local> prompt. This will display
information about fileservers, printers, and queues that
the Terminal Server has found. If a queue is in JobPoll,
the Terminal Server has successfully attached to the
queue.
The DSTree, DSContext, and
DSLicense
Type Show Protocol NetWare NDS. This command
shows the tree and the context that you have configured, a
failure code, and an NDS error code for each server.
DSTree is the directory service tree on which the Terminal Server is located. DSContext is the context where the
Terminal Server is located; it must match the context on
the file server (The DSContext must be of the following
form: ou=fruit.o=exotic). DSLicensed should be yes.
Printer and queue changes have propagated through the NDS tree
It may take a few minutes for the changes to propagate. If
the Terminal Server doesn’t attach, reboot the Terminal
Server.
Page 41
35
Table 6-3: NDS Errors from the File Server
Code Meaning Remedy
0xfffffda7 Object could not be
found in the given
context
Check the Terminal Server server name, DScontext, and
DStree to ensure the printer server is set up correctly with
PCONSOLE.
0xfffffda5 Requested attribute
could not be found
Use PCONSOLE to ensure that the Terminal Server has associated printers and the printers have associated queues.
0xfffffd69 DS Database is locked An administrator is probably updating the database. Wait a
few minutes and issue the Set Protocol NetWare Reset com-
mand.
0xfffffd63 Invalid password The password for the print server object under PCONSOLE
must match the Terminal Server login password. If the login
password on the Terminal Server is left as the default
(access), there should be no password for the print server
object.
0xfffffd54 Secure NCP violation Turn down the NCP packet signature level so that it is not
required.
Table 6-4: NDS Printing Errors
Bit Meaning Remedy
1 Server out of memory Turn the Terminal Server off, wait a few seconds, and turn it back
on. Disable unused protocols and/or remove fileservers without
print queues from the NetWare access list.
2, 3 Unexpected response
from file server
Report the problem to Black Box Technical Support.
4 No printers found for
the Terminal Server
Ensure that there are printers for the Terminal Server, and the
printer names match the service names on the Terminal Server.
Page 42
36
5 No printer queue found Ensure that the printers have associated queues.
6 Login failed Ensure there is a print server object configured with the same
name as the Terminal Server.
7 Authentication failed Ensure the Terminal Server login password is the same as the print
server object password. If the Terminal Server is using the default
password (access), there should be no print server object password.
8 Server cannot attach to
queue
Check the NDS partitions, replicas, and volumes to ensure the file
server where the queue lives has the correct information.
Table 6-4: NDS Printing Errors, cont.
Bit Meaning Remedy
Page 43
37
7: LAT Configuration
The EZWebCon configuration software is the easiest way to configure the Terminal Server.
The following sections cover print configuration methods for LAT hosts.
Note: The Terminal Server needs an IP address before you can use EZWeb-
Con. See Setting the IP Address on page 20 for instructions.
To use LAT you must obtain a LAT license from your dealer or Black Box and use the
Set/Define Protocol LAT License command on your Terminal Server. LAT print queues
can be created by printing to a port or printing to a service. Printing directly to a port
requires no Terminal Server configuration.
Note: Printing directly to a port is the easiest method for printing to the Ter-
minal Server. If you would like instructions for printing to a service,
see the Device Server Reference Manual located on the CD-ROM.
7.1 Printing Directly to a Port
1 Create a LAT application port that references the Terminal Server port.
Figure 7-1: Creating LAT Application Port
2 Create and start a print queue that uses the LAT application port.
Figure 7-2: Creating and Starting Print Queue
3 Add the commands to the SYS$MANAGER:LAT$STARTUP.COM file so the re-
quired LAT devices will be recreated after each host reboot.
Note: LAT terminal device characteristics may have to be changed to cor-
rectly print certain files. See your VMS documentation for more information.
4 Print to the queue.
Figure 7-3: Printing to Queue
$ RUN SYS$SYSTEM:LATCP
LATCP> CREATE PORT LTAnnn/APPLICATION
LATCP> SET PORT LTAnnn/NODE=LES_xxxxxx/PORT=Port_n
LATCP> EXIT
$ INITIALIZE/QUEUE/START/ON=LTAnnn:/PROCESSOR=LATSYM
/RETAIN=ERROR queue_name
$ PRINT/QUEUE=queue_name filename.txt
Page 44
38
7.2 LAT Host 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 7-4: Translating LAT Error Codes
$ SHOW QUEUE/FULL/ALL queue_name
(note the error code nnnnnnnn)
$ SET MESSAGE SYS$MESSAGE:NETWRKMSG.EXE
$ EXIT %Xnnnnnnnn
Table 7-1: Troubleshooting LAT Configurations Using a Port
Area to check Explanation
The specified node name matches the
Terminal Server node name
Use the Show Server command to verify.
The specified port name matches the
port’s name
Use the List Port 1 command to verify.
Page 45
39
8: AppleTalk Configuration
The EZWebCon configuration software is the easiest way to configure the Terminal Server.
The following sections cover print configuration methods for AppleTalk hosts.
Note: The Terminal Server needs an IP address before you can use
EZWebCon. See Setting the IP Address on page 20 for instructions.
Note: Macintoshes that do not support EtherTalk will need either an
Ethernet card or a LocalTalk-to-EtherTalk router to use the Terminal
Server.
8.1 Bitronics
Printing from a Macintosh is only possible with a PostScript printer and bi-directional
communication between the Terminal Server and that printer. The Terminal Server
supports the Bitronics interface, an extension to the standard Centronics interface. Printers
that support Bitronics allow bi-directional communication. To enable Bitronics on a
Terminal Server port, use the Define Port 2 Bitronics Enabled command.
Note: MacOS 8.1 can also print via LPD. See the Device Server Reference
Manual located on the CD-ROM and web site for configuration
instructions.
8.2 Macintosh Services
Before attempting to print from a Macintosh, ensure that AppleTalk and PostScript are both
enabled on at least one service. Once a PostScript AppleTalk service is configured, the
service will appear in the Chooser as a LaserWriter in the same zone as the Terminal
Server. Select the service in the Chooser and complete the appropriate setup options. Then
close the Chooser window and print a test page of text to the Macintosh service.
8.3 AppleTalk Zones
If there is a router on the network, the Terminal Server will appear in the default zone
specified by the router. To change the default zone use the Define Protocol AppleTalk
Zone command.
If the Terminal Server is attached to a network without an AppleTalk router, all AppleTalk
devices (including the Terminal Server) will appear in the default zone in the Chooser.
Note: If no router is present on the network, the Terminal Server will not
accept AppleTalk print jobs for 60 seconds after booting.
Page 46
40
8.4 AppleTalk Host Troubleshooting
Table 8-1: AppleTalk Host Troubleshooting
Area to Check Explanation
The printer is available to be selected
in the Chooser
Make sure the printer is in the right zone.
Bidirectional communication Lock the printer in PostScript mode and issue the
Test Service PostScript Count n command. This
sends a job to the printer and waits for the response.
Page 47
41
9: DLC Configuration for LAN
Manager
The EZWebCon configuration software is the easiest way to configure the Terminal Server.
This chapter explains DLC/Digital Network Port configuration for Windows NT 4.x hosts.
Note: The Server needs an IP address before you can use EZWebCon. See
Setting the IP Address on page 20 for instructions.
Printing using an LPD client is the preferred method for sending print jobs to the Terminal
Server. Windows 95 does not support DLC printing (see Chapter 5 for more information).
9.1 DLC Configuration
9.1.1 Terminal Server Configuration
To use the DLC protocol, you must have one service with the DLC characteristic enabled.
The DLC characteristic may be associated with only one service on a given Terminal
Server.
Figure 9-1: Enabling DLC
9.1.2 Host Configuration
To send print jobs from a Windows NT host to the Terminal Server, add the Terminal
Server as a Windows NT printer.
1 Double-click the Printers icon in the Control Panel.
2 Double-click the Add Printer icon.
3 In the window that appears, select My Computer and click Next.
4 Select the Add Port button.
5 Select Hewlett-Packard Network Port and click New Port.
If Hewlett-Packard port is not one of the available options, you must install DLC
printing from your Windows NT system disks. DLC is not installed by default.
6 Enter the Terminal Server hardware address. It is printed on the Terminal Server bot-
tom label.
Local>> DEFINE SERVICE LES_xxxxxx DLC ENABLED
Page 48
42
7 Select Job-based.
8 Select the manufacturer and printer type.
9 Enter the queue name.
10 If applicable, choose Shared and select the operating system the printer will be
working with. (First confirm that the print queue is working.)
11 Test the printer.
Page 49
43
10: Contact Information
If you are experiencing an error that is not listed in Appendix 11 or if you are unable to fix
the error, contact Black Box Technical Support at (724) 746-5500.
10.1 Problem Report Procedure
When you report a problem, please provide the following information:
Your name, and your company name, address, and phone number
Black Box Terminal Server model number
Black Box Terminal Server serial number (on the product label)
Software version (use the Show Server command to display)
Network configuration, 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)
Page 50
44
11: Troubleshooting
This Appendix discusses how to diagnose and fix errors quickly yourself without having to
contact a dealer or Black Box. It will help to connect a terminal to the serial port while
diagnosing an error to view any summary messages that are displayed.
When troubleshooting, always ensure that the physical connections (power cable, network
cable, and serial cable) are secure. If you have trouble with wireless networking (using a
third party wireless bridge, for instance) it may help to connect the Terminal Server to a
wired Ethernet network to verify that it is working properly and to check the wireless
settings separately.
Note: Some unexplained errors may be caused by duplicate IP addresses on
the network. Make sure that your Terminal Server IP address is
unique.
Page 51
45
11.1 Power-up Troubleshooting
Problem situations and error messages are listed in Table 11-1. If you cannot find an
explanation for your problem, try to match it to one of the other errors. If you cannot
remedy the problem, contact your dealer or Black Box Technical Support.
Table 11-1: Power-up Problems and Error Messages
Problem/Message Error Remedy
The Terminal Server
is connected to a
power source, but
there is no LED
activity.
The unit or its power supply is
damaged.
Contact your dealer or Black Box Technical Support for a replacement.
The Terminal Server
is unable to complete power-up diagnostics.
This generally indicates a hardware fault. One of the LEDs
will be solid red for three seconds, followed by one second of
another color.
Note the blinking LED and its color, then
contact your dealer or Black Box Technical Support. The Terminal Server will not
be operational until the fault is fixed.
The Terminal Server
completes its powerup and boot procedures, but there’s no
noticeable serial
activity.
There is a problem with the
serial connection or the set-up
of the serial device.
Check the terminal setup and the physical
connections, including the cable pinouts
(see Appendix 12). Try another serial
device or cable, or cycle power on the
Terminal Server.
A rapidly-blinking OK LED
may signal boot failure.
Reboot the unit. When the Terminal
Server is running normally, the OK LED
blinks every two seconds.
Page 52
46
The terminal shows a
Boot> prompt rather
than a Local>
prompt.
The Terminal Server is not connected properly to the Ethernet.
Ensure that the Terminal Server is firmly
connected to a functional and properlyterminated network node.
The Terminal Server Ethernet
address is invalid.
The Terminal Server Ethernet address is
located on the bottom of the unit. Use the
Change Hardware command to set the
correct address, then reboot.
Init Noboot command was
entered.
See Modem Configuration Checklist on
page 48.
The Terminal Server
passes power-up
diagnostics, but
attempts to download
new Flash ROM
code from a network
host.
If the OK LED blinks rapidly,
the Flash ROM code may be
corrupt.
Reboot the unit. If you get the same message, you will need to reload Flash ROM.
See Reloading Software on page 56.
If you did not request a TFTP
boot, the flash ROM code is
corrupt. The unit will remain in
boot mode.
Table 11-1: Power-up Problems and Error Messages, cont.
Problem/Message Error Remedy
Page 53
47
11.2 DHCP Troubleshooting
11.3 BOOTP Troubleshooting
If the BOOTP request is failing and you have configured your host to respond to the
request, check these areas:
Table 11-2: DHCP Troubleshooting
Area to Check Explanation
DHCP is enabled on the Terminal Server
Use the Set Server DHCP Enabled command.
If you manually enter an IP address, DHCP is automatically
disabled.
Make sure the DHCP server is
operational.
Check to see that the DHCP server is on and is functioning
correctly.
The Terminal Server gets its IP
address from the DHCP server
Refer to the DHCP Manager on your DHCP server for
information about addresses in use. If the DHCP server
doesn’t list your Terminal Server IP address, there may be a
problem.
Table 11-3: BOOTP Troubleshooting
Area to Check Explanation
BOOTP is in your system’s
/etc/services file
BOOTP must be an uncommented line in /etc/services.
The Terminal Server is in the
loadhost’s
/etc/hosts file
The Terminal Server must be in this file for the host to
answer a BOOTP or TFTP request.
The download file is in the correct directory and is world-readable
The download file must be in the correct directory and
world-readable. Specify the complete pathname for the
download file in the BOOTP configuration file, or add a
default pathname to the download filename.
The Terminal Server and host are
in the same IP network
Some hosts will not allow BOOTP replies across IP networks. Either use a host running a different operating system or put the Terminal Server in the same IP network as
the host.
Page 54
48
11.4 RARP Troubleshooting
11.5 Modem Configuration Checklist
Most modem problems are caused by cabling mistakes or incorrect modem configuration.
However, the following items should be verified after any modem configuration, and
rechecked when there is modem trouble.
The modem must disconnect immediately when DTR is de-asserted.
The modem must assert CD (or DSR, if connected) when connected to another mo-
dem. It must not assert CD when disconnected. The modem may optionally assert
CD during outbound dialing.
The modem and Terminal Server must agree on the flow control method and baud
rate scheme.
The modem must not send result codes or messages to the Terminal Server except
optionally during outgoing calls.
The modem should be set to restore its configuration from non-volatile memory
when DTR is dropped.
The modem should be configured to answer the phone if incoming connections are
to be supported. Generally this is done with the ats0=1 command.
The modem should not be configured to answer the phone unless the Terminal Serv-
er asserts DTR.
Table 11-4: RARP Troubleshooting
Area to Check Explanation
The Terminal Server name and hardware address in the host’s /etc/ethers
file
The Terminal Server name and hardware address
must be in this file for the host to answer a RARP
request.
The Terminal Server name and IP
address in the
/etc/hosts file
The Terminal Server name and IP address must be in
this file for the host to answer a RARP request.
The operating system Many operating systems do not start a RARP server
at boot time. Check the host’s RARPD documentation for details, or use the ps command to see if there
is a RARPD process running.
Page 55
49
Terminal Server Modem control must be enabled. Using modems on ports without
modem control enabled will lead to security problems.
The Terminal Server Autobaud feature should be enabled only when required.
11.6 Entering Commands at the Boot
Prompt
If the Boot> prompt appears on the serial console instead of the Local> prompt, one of two
things may be wrong. Either the Terminal Server does not have enough information to boot,
or the network or flash boot has failed. If pressing the Return key does not display a
prompt, press any other key. The Boot> prompt should appear.
If the Terminal Server does not have enough information to boot, or the network or flash
boot has failed, it will print a message to the console and wait ten seconds for serial port
activity. If it detects serial port activity, it will continue booting provided the flash is good.
However, if the user presses a key during that time period, the Terminal Server will display
the Boot> prompt.
Note: If you see the message “Will attempt another download in x minutes,”
press any key for the Boot> prompt.
A series of commands called Boot Configuration Program (BCP) commands can be entered
at the Boot> prompt to configure the Terminal Server. These commands are a subset of the
entire Terminal Server command set. For example, a typical TCP/IP configuration might
use the following commands:
Figure 11-1: BCP Command Examples
These commands set the Server’s address, the software loadfile, and the loadhost’s IP
address (as well as that of a backup loadhost). The server then reboots using the Flash
command and will attempt to load the file LES.SYS from the host at 192.0.1.188.
Flush NVR This command is used to restore the Terminal
Server’s non-volatile RAM to its factory default settings. It will reset everything that is
configurable on the server, including the unit’s
IP address.
Boot> SET IPADDRESS 192.0.1.229
Boot> SET SOFTWARE /tftpboot/LES.SYS
Boot> SET LOADHOST 192.0.1.188
Boot> SET SECONDARY 192.0.1.22
Boot> FLASH
% Initialization begins in 5 seconds.....
Page 56
50
Flash This command will force the Terminal Server
to download new operational code and reload it
into Flash ROM. This is necessary when a new
version of software is released and you wish to
upgrade your unit. If the server cannot download the file, the code in Flash ROM will still be
usable.
Help Displays a one-page summary of available
commands and what they do.
Init 451 Reboots the Terminal Server after it has been
configured. If the Terminal Server can find and
load the specified software loadfile, it will restart itself with full functionality. If the loadfile
is not found, the server will attempt to reload
continuously. If there is an error, or if the console’s Return key is pressed, the Terminal
Server will re-enter the Boot Configuration
Program.
SET BOOTP {Enabled, Disabled} Enables or disables the sending of BOOTP que-
ries during the boot sequence. It is enabled by
default.
SET DHCP {Enabled, Disabled} Enables or disables the sending of DHCP que-
ries during the boot sequence. It is enabled by
default.
SET Hardware xx-xx-xx Specifies the last three numbers of the server’s
Ethernet address. The first three numbers will
be supplied automatically.
The Ethernet address should have been set at
the factory. Setting an incorrect address could
cause serious network problems.
SET IPAddress ip_address Specifies this server’s IP address. Uses the stan-
dard numeric format.
SET Loadhost ip_address Specifies the host to attempt to load the file
from. The IP address should be in standard numeric format (no text names are allowed).
SET RARP {Enabled, Disabled} Enables or disables the sending of RARP que-
ries during the boot sequence. It is enabled by
default.
Page 57
51
SET Secondary ip_address Specifies a backup loadhost. The IP address
should be in standard numeric format (no text
names are allowed). The backup loadhost will
be queried if the primary host cannot load the
server.
SET Software filename Specifies the name of the file to load. the Ter-
minal Server will automatically add .SYS to the
filename you specify. Note that all protocols
must have a filename specified (either the default or set by the user). For more information,
see Appendix 13.
TCP/IP users must use the Software option to
specify the loadhost, the loadfile, and their own
network address.
TFTP users can specify a complete path name
(up to 31 characters) if the file is located in a directory other than the default. The case of the
filename must match that of the filename loaded onto the host computer.
Show Server Use this command when issuing other com-
mands to view the current Terminal Server setup.
Page 58
52
12: Pinouts
12.1 Ethernet Connector
Figure 12-1: RJ45 Ethernet Connector
12.2 RJ45 Serial Connectors
The Terminal Servers are RS-423 compliant, and are thus limited by the equipment at the
remote end of the serial line. If the is connected to an RS-232 device, it is subject to RS232 limits: 15m (50 ft.) in length at 9600 baud, and to 2m (6 ft.) at 115.2K baud, although
longer lengths will generally work.
Figure L-2: RJ45 Serial Connector
Page 59
53
12.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, you will need an RJ45-DCE DB25 adapter. The pinout
information for both connections is shown in Figure 12-3.
Figure 12-3: Pinouts of RJ45-DB25 Connections
The arrows in Figure 12-3 represent the direction of the signal. The pinouts assume that the
8-conductor cable connecting the Terminal Server and the adapter block is a swapped
cable. Both the transmit and receive ground signals on the Terminal Server connector are
wired to the signal ground on a DB25 adapter.
Figure 12-4: RJ45 to DCE DB25 Adapter
RJ45
Serial
Port
Cable
6
5
4
3
2
6
5
4
8
7
3
2
1
DTR
RX+
TX+
RX-
TX-
(out)
(out)
(in)
DSR
(in)
CTS
(in)
RTS
(out)
1
2
3
4
5
6
DCD
TXD
SG
RXD
DTR
RJ45-DB25
Adapter
RJ45 DB25
7
8
RTS
CTS
5
8
3
7
2
20
4
3
4
5
1
2
6
7
8
6
5
4
8
7
3
2
1
(Server)
(modem)
DCE - DB25 Adapter Pinout
Page 60
54
You can use a crimper block 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 12-5: Wire Splicer
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.
12.2.2 RJ45 to DB9
Figure 12-6: RJ45-DTE DB9 Adapter
RJ45 Tx Return
RJ45 Rx Return
Sealed at this end
DB9 Signal Ground
Page 61
55
The arrows in Figure 12-6 represent the direction of the signal. The pinouts assume that the
8-conductor cable connecting the Terminal Server and the adapter block is a swapped
cable. Both the transmit and receive ground signals on the Terminal Server connector are
wired to the signal ground on a DB9 adapter.
The information about crimping the RJ45 ground wires in RJ45 to DB25 applies to the DB9
connector as well.
Page 62
56
13: Updating Software
13.1 Choosing the Right Software File
Black Box intends to provide multiple software files for the Terminal Server models. Each
software file will contain the core Terminal Server operating code for that particular model.
13.2 Obtaining Software
Current software files (LES.SYS) are available on the distribution CD. You can obtain
software updates and release notes for the Terminal Server from the Black Box World
Wide Web site (www.BlackBox.com), or by using anonymous FTP through the Internet
(ftp.Black Box.com).
13.3 Reloading Software
The Terminal Server stores software in Flash ROM to control the initialization process,
operation, and command processing. The contents of Flash ROM can be updated by
downloading a new version of the operational software via NetWare, TCP/IP, or MOP.
Regardless of which protocol is used to update Flash ROM, the following points are
important:
The Flash ROM software file name, LES.SYS, should not be changed.
The download file should be world-readable on the host.
There is a sixteen character length limit for the path name.
There is a twelve character limit for the filename.
Define commands must be used because Set configurations are cleared when the
Terminal Server boots. Use the List Server Boot command to check settings before
rebooting.
Table 13-1: Available Terminal Server Software
Software File Name Models Supported
LES2700A_16.SYS LES2700A-16-R3
LES2700A_32.SYS LES2700A-32-R3
Page 63
57
Note: It is important to check Terminal Server settings before using the Ini-
tialize Reload command to ensure that you are reloading the correct
software file.
13.3.1 Reloading Sequence
If DHCP, BOOTP, or RARP is enabled on the Terminal Server, the Terminal Server will
request assistance from a DHCP, BOOTP, or RARP server before starting the download
attempts. the Terminal Server 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 the download file cannot be found or accessed,
the Terminal Server can be rebooted with the code still in Flash ROM. The OK/ACT LED
will blink quickly while the Terminal Server is booting (and reloading code) and then
slowly when it returns to normal operation.
Note: If you experience problems reloading Flash ROM, refer to Trouble-
shooting Flash ROM Updates on page 59.
13.3.1.1 TCP/IP
Before the Terminal Server downloads the new software, it will send DHCP, BOOTP, and/
or RARP queries (all are enabled by default). Next, the Terminal Server will attempt to
download the LES.SYS file using TFTP (Trivial File Transfer Protocol).
Note: EZWebCon can also be used to reload software.
If a host provides DHCP, BOOTP, or RARP support, it can be used to set the Terminal
Server IP address (all methods) and loadhost information (BOOTP and RARP only).
Some BOOTP and TFTP implementations require a specific directory for the LES.SYS
file. See your host’s documentation for instructions.
To manually configure the Terminal Server IP parameters for software reload, use the
following commands.
Figure 13-1: Configuring TCP/IP Reload
Note:
For instructions on how to log into the Terminal Server to enter these
commands, see the Getting Started chapter.
Local> SET PRIVILEGED
Password> SYSTEM (not echoed)
Local>> DEFINE SERVER IPADDRESS nnn.nnn.nnn.nnn
Local>> DEFINE SERVER SOFTWARE “/tftpboot/LES.SYS”
Local>> DEFINE SERVER LOADHOST nnn.nnn.nnn.nnn
Local>> LIST SERVER BOOT
Local>> INITIALIZE RELOAD
Page 64
58
The path and filename are case-sensitive and must be enclosed in quotation marks. When
attempting to boot across an IP router, you must configure the router to proxy-ARP for the
Terminal Server, or use the bootgateway feature. For more information, see Set/Define
Bootgateway in the Commands chapter of the Device Server Reference Manual located on
the CD-ROM.
13.3.1.2 NetWare
The LES.SYS file should be placed in the login directory on the NetWare file server. the
Terminal Server cannot actually log into the file server (since it knows no username/
password); it can only access files in the login directory itself. On the Terminal Server,
specify the file server name, filename, and path.
Figure 13-2: Configuring NetWare Reload
13.3.1.3 MOP
The LES.SYS filename is the only parameter that the Terminal Server needs to reload via
MOP. Make sure the service characteristic is enabled on the host's Ethernet circuit, copy
the LES.SYS file to the MOM$LOAD directory, and reload the Terminal Server using the
Initialize Reload command. Be sure to use binary mode for the file transfer.
Local> SET PRIVILEGED
Password> SYSTEM (not echoed)
Local>> DEFINE SERVER NETWARE LOADHOST fileserver
Local>> DEFINE SERVER SOFTWARE SYS:\LOGIN\LES.SYS
Local>> INITIALIZE RELOAD
Page 65
59
13.4 Troubleshooting Flash ROM Updates
Many of the problems that occur when updating the Flash ROM can be solved by
completing the following steps:
Table 13-2: Flash ROM Troubleshooting
Protocol Area to Check
NetWare Ensure the file is in the login directory. Since the Terminal Server cannot actually
log into the file server, it has very limited access to the server directories.
TFTP Check the file and directory permissions.
Ensure the loadhost name and address are specified correctly and that their case
matches that of the filenames on the host system.
Ensure the file and pathnames are enclosed in quotes to preserve case.
Ensure that TFTP is enabled on the host; several major UNIX vendors ship their
systems with TFTP disabled by default.
MOP The Ethernet circuit must have the service characteristic enabled.
Ensure that the MOM$LOAD search path includes the directory containing the
LES.SYS file.
Page 66
60
14: Specifications
14.1 Power Information
14.1.1 Power Requirements
Voltage: 110 V AC US, 220 V AC International
Frequency: 47-63 Hz
Operating Current: 700 mA @ 6 V
Power Consumption: 4.2 Watts (maximum)
Fuse Rating 1.6A, 250 Volts
14.1.2 Power Supply Cord
Cord type: 3 conductors, 1.0 mm2 minimum conductor
size (approximately 18 AWG)
Rated for: 250 Volts AC, 10 Amps
Length: 3.0 meters
14.2 Environmental Limitations
14.2.1 Temperature
Operating range: 5° to 50° C (41° to 122° F)
Storage range: -40° to 66° C (-40° to 151° F)
Max temp. change/hr: 20° C (36° F)
Rapid temperature changes may affect operation. Therefore, do not operate the Terminal
Server near heating or cooling devices, large windows, or doors that open to the outdoors.
14.2.2 Altitude
Operating maximum: 2.4 km (8,000 ft)
Page 67
61
Storage maximum: 9.1 km (30,000 ft)
If operating the Terminal Server above 2.4 km (8000 ft.), decrease the operating
temperature rating by 1° F for each 1000 ft.
14.2.3 Relative Humidity
Operating range: 10% to 90% noncondensing, 40% to 60% rec-
ommended
Storage range: 10% to 90% noncondensing
Page 68
62
15: Frequently-used
Commands
This appendix lists some of the most frequently-used commands of the Multiport Device
Server command set. More information about the command set, including additional
options, can be found in the Device Server Reference Manual located on the CD-ROM.
15.1 Conventions
Please note the following before continuing:
Commands are divided into Server (general), Port, and Protocol sections. Within
each section, commands are listed alphabetically.
Commands may require privileged user status. Enter Set Privileged, then enter the
privileged password when prompted.
When you enter a Define (or Purge) command, you must reboot the Terminal Server
for the command to take effect. Alternately, you can issue several Set commands and
then a Save command to make the Set commands take effect without rebooting.
When the abbreviated syntax “{EN/DIS}” is shown, you must choose either En-
abled or Disabled to complete the command.
When 2 is shown as the port number, enter a single port number, a list of port num-
bers separated by commas, a range of port numbers separated by dashes, or the word
all.
Page 69
63
15.2 Server Commands
Table 15-1: Frequently-used Server Commands
Command Option(s) Description
CONNECT option servicename Makes a connection to a LAT service.
LOCAL num Makes a connection to the specified local port.
RLOGIN host Makes an Rlogin connection to the specified
host (text name or numeric IP address).
TCP host Makes a raw TCP connection to the specified
host (text name or numeric IP address).
TELNET host Makes a Telnet connection to the specified host
(text name or numeric IP address).
DEFINE SERVER BOOTP {EN/DIS} Enables or disables querying for a BOOTP host
at system boot time.
DEFINE SERVER DHCP {EN/DIS} Enables or disables querying for a DHCP host at
system boot time.
DEFINE SERVER GATEWAY ipaddr Specifies the host to be used as a TCP/IP gate-
way to forward packets between networks.
Enter an IP address.
DEFINE SERVER
INCOMING option
BOTH Enables incoming LAT and Telnet connections.
LAT Enables only incoming LAT connections.
NONE Disables incoming connections.
TELNET Enables only incoming Telnet connections.
PASSWORD Causes the Terminal Server to prompt for a
password for all incoming connections.
NOPASSWORD Allows connections to be established without
prompting for a password.
DEFINE SERVER IPADDRESS ipaddr Sets the Terminal Server ’s network IP address.
DEFINE SERVER LOADHOST ipaddr Specifies the TCP/IP host from which the Ter-
minal Server requests its run-time code.
DEFINE SERVER LOGIN PASSWORD Sets a new password that will be required before
incoming logins are accepted. You will be
prompted for the new password (up to 6 characters, case-insensitive).
DEFINE SERVER NAME “newname” Specifies a new name for the Terminal Server.
Names are restricted in length; generally a name
of 11 or fewer characters is permissible.
Page 70
64
DEFINE SERVER NETWARE LOADHOST
server
Specifies the NetWare host from which the Terminal Server requests its run-time code. Enter a
file server name of up to 11 characters.
DEFINE SERVER PRIVILEGED PASSWORD Sets a new password that will be required for
privileged user status. You will be prompted for
the new password (up to 6 characters, caseinsensitive).
DEFINE SERVER RARP {EN/DIS} Enables or disables querying for a RARP host at
system boot time.
DEFINE SERVER SOFTWARE “filename” Specifies the name or path (TCP) of the soft-
ware download file. The filename can be up to
11 characters, and the pathname can be up to 26.
The Terminal Server will add a “.SYS” extension.
DEFINE SERVER SUBNET MASK ipmask Specifies the subnet mask to be used for the Ter-
minal Server. The ipmask must be in n.n.n.n
format.
HELP option <nothing> Displays a list of top-level (general) Help top-
ics.
<keyword> Displays information about the keyword(s)
entered. Multiple keywords must be specified in
the order they occur in a command.
DEFINE SERVICE “name” PORT num Creates a new service and associates it with the
specified port.
DEFINE SERVICE
“name” option
APPLETALK {EN/DIS} Toggles whether the named service can be used
to service networks running the specified protocol. RTEL applies to TCP/IP networks.
LANMAN {EN/DIS}
LAT {EN/DIS}
NETWARE {EN/DIS}
RTEL {EN/DIS}
Table 15-1: Frequently-used Server Commands, cont.
Command Option(s) Description
Page 71
65
DEFINE SERVICE
“name” option
DLC {EN/DIS} Specifies which service will handle print
requests from DLC hosts. DLC can be enabled
on one service per Terminal Server.
BANNER {EN/DIS} When Enabled, causes the Terminal Server to
print a banner page before jobs.
BINARY {EN/DIS} When Enabled, the Terminal Server will not
process data passed through the service. This
characteristic should be enabled when printing
PCL data.
EOJ string Causes the Terminal Server to send an end-of-
job string to the attached device after every job.
Enter an end string or the word none.
FORMFEED {EN/DIS} When Enabled, causes the Terminal Server to
append a formfeed to the end of LPR print jobs.
POSTSCRIPT
{EN/DIS}
When Enabled, causes the Terminal Server to
assume the attached device is a PostScript
device and act accordingly.
PSCONVERT {EN/DIS} When Enabled, causes the Terminal Server to
place a PostScript wrapper around each job.
SOJ string Causes the Terminal Server to send a start-of-
job string to the attached device before every
job. Enter a start string or the word none.
DEFINE SERVICE
“name” option
TCPPORT string Specifies a raw TCP listener socket for the ser-
vice. Enter a socket number (4000 to 4999) or
the word none.
TELNETPORT string Specifies a TCP listener socket for the service.
Unlike TCPport, this option performs Telnet
IAC interpretation on the data stream. Enter a
socket number (4000 to 4999) or the word none.
INITIALIZE option DELAY num Schedules a reboot after num minutes. Enter a
value from 0 to 120.
CANCEL Cancels an impending initialization.
FACTORY Reboots the Terminal Server to its factory
default settings.
NOBOOT Forces the Terminal Server to stop in Boot Con-
figuration Mode rather than fully rebooting.
RELOAD Forces the Terminal Server to download new
operational code and reprogram its flash-ROM.
Table 15-1: Frequently-used Server Commands, cont.
Command Option(s) Description
Page 72
66
LOGOUT option <nothing> Logs out the current port (the port that issued
the command).
PORT num Logs out the specified port.
PURGE SERVICE
option
LOCAL Removes the definitions of all local services.
“service” Removes the definition of the specified service.
SET PRIVILEGED Enters privileged mode, provided the user enters
the proper privileged password when prompted.
{SHOW/MONITOR} QUEUE Displays the status of Terminal Server queues
once (Show) or continually every three seconds
(Monitor).
{SHOW/MONITOR}
SERVER
<nothing> Displays Terminal Server information once
(Show) or continually every three seconds
(Monitor).
COUNTERS Displays characteristics related to the various
counters kept by the Terminal Server.
{SHOW/MONITOR}
SERVICE option
<nothing> Displays characteristics about all configured
services once (Show) or continually every three
seconds (Monitor).
“service” Displays only characteristics related to the
named service.
ZERO COUNTERS
option
ALL Zeroes all port, node, and server counters.
PORT num Zeroes port counters for the specified port.
Table 15-1: Frequently-used Server Commands, cont.
Command Option(s) Description
Page 73
67
15.3 Port Commands
In the following commands, “2” can be a single port number, a list of port numbers
separated by commas, a range of port numbers separated by dashes, or the word all.
Table 15-2: Frequently-used Port Commands
Command Option(s) Description
DEFINE PORT 2
ACCESS option
DYNAMIC The port can initiate and receive connection
requests.
LOCAL The port can initiate connection requests, and local
logins are permitted.
NONE The port is unusable.
REMOTE The port can receive host-initiated connection
requests.
DEFINE PORT 2 BITRONICS {EN/DIS} When Enabled, ensures bidirectional functioning of
the parallel port. The attached printer must also support Bitronics mode.
DEFINE PORT 2 CHARACTER size Toggles the port between 7-bit and 8-bit characters
(the default). Enter either 7 or 8.
DEFINE PORT 2 DSRLOGOUT {EN/DIS} When Enabled, the port will be logged out automat-
ically whenever DSR is deasserted.
DEFINE PORT 2 DTRWAIT {EN/DIS} When Enabled, the Terminal Server will not assert
DTR on the port when it is idle (no user logins or
connections).
DEFINE PORT 2 FLOW
option
CTS Specifies CTS/RTS (hardware) flow control.
{EN/DIS} Activates or deactivates the currently-configured
flow-control method.
NONE Removes the current flow control settings.
XON Specifies XON/XOFF (software) flow control.
DEFINE PORT 2 NAME “newname” Enter a name of up to 16 alphanumeric characters
for the specified port.
DEFINE PORT 2
PAR IT Y option
parity Enter even, odd, mark, or space. Specifying mark
or space will change the character size to 7 bits.
NONE Specifies that no parity will be used (the default).
DEFINE PORT 2 SPEED baudnum Sets the port’s baud rate. Acceptable baudnum val-
ues range from 300 to 230000 baud.
Page 74
68
15.4 Protocol Commands
In the following table, PROTO is an abbreviation for the optional keyword PROTOCOL.
{SHOW/MONITOR} PORT 2 Displays the port’s configuration characteristics
once (Show) or continually every three seconds
(Monitor). Counters and Status keywords can be
added.
TEST PORT 2 option COUNT rows
WIDTH cols
Sends an ASCII data stream to the port for the specified number of rows and/or columns.
POSTSCRIPT Sends a PostScript test page to the port.
Table 15-3: Frequently-used Protocol Commands
Command Option(s) Description
DEFINE PROTO
APPLETALK option
{EN/DIS} Enables or Disables the AppleTalk protocol for
the Terminal Server.
ZONE newzone Places the Terminal Server in a zone other than
the default.
DEFINE PROTO IP
option
{EN/DIS} Enables or Disables the TCP/IP protocol for the
Terminal Server.
GATEWAY ipaddr See DEFINE SERVER GATEWAY ipaddr.
IPADDRESS ipaddr See DEFINE SERVER IPADDRESS ipaddr.
LOADHOST ipaddr See DEFINE SERVER LOADHOST ipaddr.
NAMESERVER ipaddr Specifies the IP address of the host that will
resolve text host names into their numeric equivalents for TCP/IP connection attempts.
DEFINE PROTO
LANMAN option
{EN/DIS} Enables or Disables the LAN Manager protocol
for the Terminal Server.
DEFINE PROTO LAT
option
{EN/DIS} Enables or Disables the LAT protocol for the
Terminal Server.
LICENSE string Enables LAT on multi-port Terminal Servers.
Enter the license string obtained from Black Box.
Table 15-2: Frequently-used Port Commands, cont.
Command Option(s) Description
Page 75
69
DEFINE PROTO
NETWARE option
{EN/DIS} Enables or Disables the NetWare (IPX) protocol
for the Terminal Server.
DSCONTEXT string Configures the NetWare Directory Services con-
text in which the Terminal Server is located. For
more information about NDS contexts, see your
NDS documentation.
DSLICENSE string Configures the NetWare Directory Services
license needed to enable NDS on your Terminal
Server. Enter the license string obtained from
Black Box.
DSTREE string Configures the NetWare Directory Services tree
in which the Terminal Server is located. For more
information about NDS trees, see your NDS documentation.
DEFINE PROTO
NETWARE
ENCAPSULATION
option {EN/DIS}
NATIVE Configures the Terminal Server to use the “native
mode” frame format.
ETHER_II Configures the Terminal Server to use Ethernet
v2 frame format.
802_2 Configures the Terminal Server to use 802.2
frame format with NetWare SAPs.
SNAP Configures the Terminal Server to use 802.2
frame format with SNAP SAPs.
DEFINE PROTO NETWARE LOADHOST
server
See DEFINE SERVER NETWARE LOADHOST
server.
PURGE IPSECURITY
option
ALL Removes the entire IP security table.
ipaddress Removes entries from the IP security table that
are related to the specified IP address.
PURGE PROTO NETWARE ACCESS
option
ALL Removes all entries from the NetWare access list.
server Removes entries from the NetWare access list that
are related to the specified file server.
{SHOW/MONITOR} PROTO protocolname Displays operating characteristics of the specified
protocol.
Table 15-3: Frequently-used Protocol Commands, cont.
Command Option(s) Description
Page 76
70
Declaration of Conformity
(according to ISO/IEC Guide 22 and EN 45014)
Manufacturer’s Name & Address: Black Box Corporation
1000 Park Drive, Lawrence, PA 15055 USA
Declares that the product:
Product Name: 16-Port Rackmount 10/100 Serial Terminal
Server and 32-Port Rackmount 10/100 Serial
Terminal Server
Model Name/Number:
LES2700A-16-R3
LES2700A-32-R3
Conforms to the following standards or other normative documents:
Safety: EN 60950:1988 + A1, A2
Electromagnetic Emissions: EN55022: 1998 (CISPR 22, Class A: 1993, A1:
1995, A2: 1996)
IEC 1000-3-2/A14: 2000
IEC 1000-3-3: 1994
Electromagnetic Immunity
EN55024: 1998 Information Technology EquipmentImmunity Characteristics
IEC 6100-4-2: 1995 Electro-Static Discharge Test
IEC 6100-4-3: 1996 Radiated Immunity Field Test
IEC 6100-4-4: 1995 Electrical Fast Transient Test
IEC 6100-4-5: 1995 Power Supply Surge Test
IEC 6100-4-6: 1996 Conducted Immunity Test
IEC 6100-4-8: 1993 Magnetic Field Test
IEC 6100-4-11: 1994 Voltage Dips & Interrupts Test
(L.V.D. Directive 73/23/EEC)
Supplementary Information: The product complies with the requirements of
the Low Voltage Directive 72/23/EEC and the
EMC Directive 89/336/EEC.
Manufacturer’s Contact: Black Box Corporation
1000 Park Drive, Lawrence, PA 15055 USA
General Tel: 724/746-5500
Fax: 724/746-0746
Page 77
71
FCC Requirements for
Telephone-Line Equipment
1. The Federal Communications Commission (FCC) has established rules which permit
this device to be directly connected to the telephone network with standardized jacks. This
equipment should not be used on party lines or coin lines.
2. If this device is malfunctioning, it may also be causing harm to the telephone network;
this device should be disconnected until the source of the problem can be determined and
until the repair has been made. If this is not done, the telephone company may temporarily
disconnect service.
3. If you have problems with your telephone equipment after installing this device,
disconnect this device from the line to see if it is causing the problem. If it is, contact your
supplier or an authorized agent.
4. The telephone company may make changes in its technical operations and procedures.
If any such changes affect the compatibility or use of this device, the telephone company
is required to give adequate notice of the changes.
5. If the telephone company requests information on what equipment is connected to their
lines, inform them of:
a. The telephone number that this unit is connected to.
b. The ringer equivalence number.
c. The USOC jack required: RJ-11C
d. The FCC registration number.
Items (b) and (d) can be found on the unit’s FCC label. The ringer equivalence number
(REN) is used to determine how many devices can be connected to your telephone line. In
most cases, the sum of the RENs of all devices on any one line should not exceed five
(5.0). If too many devices are attached, they may not ring properly.
6. In the event of an equipment malfunction, all repairs should be performed by your supplier or an authorized agent. It is the responsibility of users requiring service to report the
need for service to the supplier or to an authorized agent.
Page 78
72
Certification Notice for
Equipment Used in Canada
The Canadian Department of Communications label identifies certified equipment. This
certification means that the equipment meets certain telecommunications-network
protective, operation, and safety requirements. The Department does not guarantee the
equipment will operate to the user’s satisfaction.
Before installing this equipment, users should ensure that it is permissible to be connected
to the facilities of the local telecommunications company. The equipment must also be
installed using an acceptable method of connection. In some cases, the company’s inside
wiring associated with a single-line individual service may be extended by means of a
certified connector assembly (extension cord). The customer should be aware that
compliance with the above conditions may not prevent degradation of service in some
situations.
Repairs to certified equipment should be made by an authorized Canadian maintenance
facility-- in this case, your supplier. Any repairs or alterations made by the user to this
equipment, or equipment malfunctions, may give the telecommunications company cause
to request the user to disconnect the equipment. Users should ensure for their own
protection that the electrical ground connections of the power utility, telephone lines, and
internal metallic water pipe system, if present are connected together. This precaution may
be particularly important in rural areas.
CAUTION:
Users should not attempt to make such connections themselves, but should contact the
appropriate electric inspection authority, or electrician, as appropriate.
The LOAD NUMBER (LN) assigned to each terminal device denotes the percentage of
the total load to be connected to a telephone loop which is used by the device, to prevent
overloading. The termination on a loop may consist of any combination of devices, subject only to the requirement that the total of the load numbers of all the devices does not
exceed 100.
Page 79
73
Federal Communications
Commission and Canadian
Department of
Communications Radio
Frequency Interface
Statements
This equipment generates, uses, and can radiate radio frequency energy and if not installed
and used properly, that is, in strict accordance with the manufacturer's instructions, may
cause interference to radio communication. It has been tested and found to comply with the
limits for a Class A computing device in accordance with the specifications in Subpart B
of Part 15 of FCC rules, which are designed to provide reasonable protection against such
interference when the equipment is operated in a commercial environment. Operation of
this equipment in a residential area is likely to cause interference, in which case the user at
his own expense will be required to take whatever measures may be necessary to correct
the interference.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
This digital apparatus does not exceed the Class A limits for radio noise emission from
digital apparatus set out in the Radio Interference Regulation of the Canadian Department
of Communications.
Le présent appareil numérique n'émet pas de bruits radioélectriques dépassant les limites
applicables aux appareils numériques de la classe A prescrites dans le Règlement sur le
brouillage radioélectrique publié par le ministère des Communications du Canada.
Page 80
74
Normas Oficiales Mexicanas
(NOM)
Electrical Safety Statement
Instrucciones de Seguridad
1 Todas las instrucciones de seguridad y operación deberán ser leídas antes de que el
aparato eléctrico sea operado.
2 Las instrucciones de seguridad y operación deberán ser guardadas para referencia
futura.
3 Todas las advertencias en el aparato eléctrico y en sus instrucciones de operación de-
ben ser respetadas.
4 Todas las instrucciones de operación y uso deben ser seguidas.
5 El aparato eléctrico no deberá ser usado cerca del agua—por ejemplo, cerca de la
tina de baño, lavabo, sótano mojado o cerca de una alberca, etc.
6 El aparato eléctrico debe ser usado únicamente con carritos o pedestales que sean re-
comendados por el fabricante.
7 El aparato eléctrico debe ser montado a la pared o al techo sólo como sea re-
comendado por el fabricante.
8 Servicio—El usuario no debe intentar dar servicio al equipo eléctrico más allá a lo
descrito en las instrucciones de operación. Todo otro servicio deberá ser referido a
personal de servicio calificado.
9 El aparato eléctrico debe ser situado de tal manera que su posición no interfiera su
uso. La colocación del aparato eléctrico sobre una cama, sofá, alfombra o superficie
similar puede bloquea la ventilación, no se debe colocar en libreros o gabinetes que
impidan el flujo de aire por los orificios de ventilación.
10 10.El equipo eléctrico deber ser situado fuera del alcance de fuentes de calor como
radiadores, registros de calor, estufas u otros aparatos (incluyendo amplificadores)
que producen calor.
11 El aparato eléctrico deberá ser connectado a una fuente de poder sólo del tipo descri-
to en el instructivo de operación, o como se indique en el aparato.
12 Precaución debe ser tomada de tal manera que la tierra fisica y la polarización del
equipo no sea eliminada.
Page 81
75
13 Los cables de la fuente de poder deben ser guiados de tal manera que no sean pisados
ni pellizcados por objetos colocados sobre o contra ellos, poniendo particular atención a los contactos y receptáculos donde salen del aparato.
14 El equipo eléctrico debe ser limpiado únicamente de acuerdo a las recomendaciones
del fabricante.
15 En caso de existir, una antena externa deberá ser localizada lejos de las lineas de en-
ergia.
16 El cable de corriente deberá ser desconectado del cuando el equipo no sea usado por
un largo periodo de tiempo.
17 Cuidado debe ser tomado de tal manera que objectos liquidos no sean derramados
sobre la cubierta u orificios de ventilación.
18 Servicio por personal calificado deberá ser provisto cuando:
A El cable de poder o el contacto ha sido dañado; u
B Objectos han caído o líquido ha sido derramado dentro del aparato; o
C El aparato ha sido expuesto a la lluvia; o
D El aparato parece no operar normalmente o muestra un cambio en su desem-
peño; o
E El aparato ha sido tirado o su cubierta ha sido dañada.
Page 82
76
Index
Symbols
/etc/hosts 30
Numerics
10BASE-T port 11, 12
A
Access list, NetWare 41
ACT LED 55
AppleTalk 48–49
Chooser 48
Configuration 48
Router 48
Troubleshooting 49
Zones 48, 49
Application port, LAT 45
Applications 21
ARP table 30
AUI port 11, 12
B
Back panel 11, 12
Banner 31, 39
BCP (Boot Configuration Program) 59
Bindery 40
Bitronics 11, 48
Boot prompt 54, 59
BOOTP 29, 31, 44, 68
Troubleshooting 58
Bracket, rack mount 17
C
Centronics 11, 48
Chooser (Macintosh) 48
CLI (Command Line Interface) 29, 31
Page 83
77
Comm Port Redirector 28
Commands 72–78
Components, description of 9
Configuration
AppleTalk
48
Initial setup 19
LAN Manager 50
LAT 45
NetWare 40
TCP/IP 29
Console terminal 20
Contact information 52
D
DB25 63
DB25 ports 11, 12
DB9 64
Defaults, restoring 59
DHCP 31, 57, 60, 68
Troubleshooting 57
Digital Network Port 50
Displaying current settings 61
DLC 50
DOS 30
Download file 58
E
Error codes, LAT 46
Ethernet
Address
60
Ethernet address 30
Ethernet connector 62
Ethernet, connecting to 14, 17
EtherTalk 48
EZWebCon 14, 18, 19, 29, 40, 45, 48, 50
F
Factory defaults 59
Filters, input/output 32
Page 84
78
Flash 55, 67
Troubleshooting 69
Updates 56, 67
Flash ROM 56
Reloading 59
Flush NVR 59
Front panel 9
FTP 19, 66
H
Hardware address 30, 58, 60
I
Incoming logins 20
Installation
Installation, testing
18
Introduction 7
IP
UDP
28
IP address 19, 29, 35, 40, 45, 48, 50, 54, 58
Configuring 29, 60
Configuring via BOOTP 31
Configuring via command line 31
Configuring via DHCP 31
Configuring via Ping 29
Configuring via RARP 31
IPX (NetWare) 40–43
J
Java 19
L
LAN Manager 50–51
Configuration 50
Black Box
Contact information
52
Technical support 40, 52
Web site 40
LAT 20, 45
Page 85
79
Application port 45
Error codes 46
License 45
Printing to port 45
Printing to service 45
Queue 45
Troubleshooting 46
LEDs 9, 16, 55, 56
Loadfile 61
Loadhost 60
Local prompt 56
Local> prompt 20, 29
LocalTalk 48
Login
Web browser
19
Logins
Incoming
20
Password 19, 20
Remote console 19
Service 20
lpc 39
LPD 36, 48, 50
LPR 31, 36
AIX 36
HP 37
Print command 36
SCO Unix 38
UNIX (Generic) 35
Windows NT 32
lpstat 39
M
Macintosh 48
Chooser 48
EtherTalk 48
LocalTalk 48
OS 8.1 and LPD 48
Zones 49
MOP
Reloading software
69
Page 86
80
N
Named pipe interface 32
Nameserver 30
NDPS 40
NDS 40
Directory service context 41
Directory service tree 41
License 40, 41
NetWare 40–43
Access list 41
Administrator 40, 41
Bindery 40
NDS 40, 41
PCONSOLE 42
Reloading software 69
Troubleshooting 43
NVR 9
NVRAM 59
P
Parallel port
Service
20
Passwords
Login
19, 20
Privileged 19, 72
PCONSOLE 40, 42
Ping 29
Pinouts 62
Ports
Serial
62
PostScript 48
Power
Cord
70
Specifications 70
Troubleshooting 55
Power plug 11, 12
Power switch 9
Power-up troubleshooting 56
Print pipe 39
Page 87
81
Print queue 20, 32, 37, 38, 42, 45, 51
Printcap file 39
Printing to a queue 36, 37, 46
Privileged password 19, 72
Problem report procedure 52
Prompt, Local> 20
Prompts
Boot
54, 59
Local 56
Protocols 7
AppleTalk 48
LAN Manager 50
LAT 45
NetWare 40
TCP/IP 29
Protocols supported 7
Q
QINST 40
Queue 7, 20, 32, 37, 38, 40, 41, 42, 45, 51
R
Rack mount bracket 17
RARP 29, 31, 58, 60, 68
RARPD process 58
Troubleshooting 58
Rebooting 60
Redirector 28
Reloading software 59, 67
MOP 69
NetWare 69
TCP/IP 68
Remote console logins 19
Remote printer 20
Remote queue 20
Reset/Test button 55
Restoring defaults 59
RJ45 62, 63, 64
RJ45 ports 11, 12
Page 88
82
RS-232 62
RS-423 62
RTEL 31, 32, 39
S
SAM 37
Serial port
Connectors
62
Service 20
Serial ports 11, 12
Serial tunnel 27
Server 19
Name, default 39
Service 19, 20, 42, 45, 48
Name 39
SMIT 36
Software file 58, 67
Software updates 66
FTP 66
Web 66
Specifications 70
Altitude 70
Environmental 70
Power 70
Relative Humidity 71
Temperature 70
Spooling directory 32
System Administration Mgr (SAM) 37
System Mgmt Interface Tool (SMIT) 36
T
TCP/IP 29–39, 50, 54
Reloading software 68
Telnet 20, 30, 39
Test button 9
Test/Reset button 55
TFTP 68
ThinWeb Manager 19
Troubleshooting 54–61
Page 89
83
AppleTalk 49
BOOTP 58
DHCP 57
Flash (software) updates 69
LAT 46
NetWare 43
Power-up 55, 56
RARP 58
Unix 39
Tunnel, serial 27
U
UDP 28
UNIX named pipe interface 39
Updating software 66
V
VMS 45, 46
W
Web browser interface 19
Windows 30, 31, 50
Z
Zones, AppleTalk 48, 49
Page 90
Loading...