Getting Started 37
Setting Up the Network
z
Printing
—(Secure Terminal Server/Secure Device Server/Secure Console Server models only)
Allows hosts on the network to talk to a printer connected to the Terminal Server, using LPD.
z
Raw TCP
—Allows hosts on the network to communicate with a serial device that requires raw
data throughput (such as a printer or card reader) connected to the Terminal Server serial port.
z
Console Management
—Allows users on the network to connect to the console port of a server
that is connected to a serial port on the Terminal Server.
z
Secure Console Management
—(Secure Terminal Server/Secure Device Server/Secure Console
Server models only) Allows users on the network to securely connect to the console port of a
server that is connected to a serial port on the Terminal Server.
z
Terminal
—Allows a terminal device connected to a serial port on the Terminal Server, to
connect to a specified host on the Network.
z
Virtual COM Port (Client-Initiated)
—Allows a serial application running on a networked
system to communicate with a serial device attached to the Terminal Server as if it was directly
attached to the networked system. The networked system must be running the COMredirect
software. Use this option if the networked system will be initiating the network connection to
the Terminal Server.
z
Virtual COM Port (Server-Initiated)
—Allows a serial application running on a networked
system to communicate with a serial device attached to the Terminal Server as if it was directly
attached to the networked system. The networked system must be running the COMredirect
software. Use this option if the Terminal Server will be initiating the network connection to the
networked system
Setting Up the Network
The most important part of setting up the network is assigning an IP address to the Terminal Server,
whether this is a static IP address or enabling a DHCP/BOOTP-assigned IP address. You should also
assign a name to the Terminal Server, to make it easier to recognize. This section deals primarily with
setting the IP address.
Using DeviceManager
To use the DeviceManager, you must first install it on a Windows operating system. The
DeviceManager is able to automatically discover all Terminal Servers on your local network, even if
they have not yet been assigned an IP address. If routers on the network have been setup to propagate
multicasts, DeviceManager will also be able to discover Terminal Server's in other networks. The
DeviceManager installation wizard can be found on the CD-ROM included in the Terminal Server
package.
1.
Connect the Terminal Server to the network.
2.
Power on the Terminal Server.
3.
From the CD-ROM that was included in the Terminal Server packaging, select the
DeviceManager link.
4.
Click on the link under
Location
and click
Open
to automatically start the DeviceManager
installation.
5.
Install the DeviceManager by following the installation wizard. On the last window, check the
Yes, I want to launch DeviceManager now.
box and click the
Finish
button.
6.
When you launch the DeviceManager, it will automatically scan the local network and display
any Terminal Servers that it can find.
7.
Any Terminal Server that does not have an IP address will be displayed as
Not Configured
, with
the
Model
and
MAC Address
to identify the Terminal Server. Highlight the Terminal Server that
you want to assign an IP address to and click the
Assign IP
button.
