Changing a host defined to the Redirector
To change a host that has been defined to the Redirector:
- Click Redirector Service in the Administration window.
- Highlight the host configuration you want to change.
- Click Change.
- Make the necessary changes.
- Click OK to save your changes.
- Destination Address
- The host name or IP address of the target Telnet server. If the IP address is
likely to change, use the host name.
- Destination Port
- The port number for the Telnet server through which it will communicate with the
Many hosts use the default, which is 23, for Telnet connections.
- Local Port
- The port number through which the Redirector will communicate with clients.
Use the standard default port numbers or
devise a new numbering scheme. When devising a new scheme, use port
numbers that are not already defined for other TCP/IP applications. Because
most well-known port numbers are lower than 5000, pick a port number between
5000 and 65535 to avoid conflicts. You must configure the firewalls in your network to allow
traffic on the port you choose.
- Select a security level. Security through the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocol
must be set separately for each host configuration. The choices are:
- Client-side - provides encryption of data transmitted between the Redirector and the emulator
- Host-side - provides encryption of data transmitted between the Redirector and a secure server (host)
- Both - provides encryption of data transmitted through the Redirector, between the emulator and a secure server (host)
- Client Authentication:
- This option is enabled only if the Redirector is configured to use Java Secure Socket Extension (JSSE). This will enable redirector to request Client certificate during handshake process for improved security. Refer to Adding a host to the Redirector for information on how to configure JSSE for Redirector on Windows.
- Log Connections
- Select Yes if you want to save Redirector connection information in a log file. For each connection from the client,
there is a corresponding connection to the host. The log file contains the IP address, port, and the state of the
connection. The following table defines the different connection states:
If the state of the connection is not attemped, the connection failed to open or did not attempt to open because of another
error, for example, the client connection failed to open and therefore the host connection was not attempted.
The default is No. You must
stop and restart the Redirector to begin logging connections.
- If you select Yes for Log Connections, you can specify a directory and name for the log file. If you do not specify a directory,
the log file is created in \ZIEForWeb\lib. If you do not specify a file name,
a window appears asking you to specify a file name.
- Rollback Size
- If you select Yes for Log Connections, you can specify a maximum size (bytes) for the log file. When the log file reaches
the size you specify, any existing Redirector connection information is deleted and new Redirector connection information is
logged at the beginning of the file. The default is 65536 bytes.
- Select Yes if you want the Redirector connection to remain active during a period of inactivity. Keep-Alive requires Java 2 on
all operating systems except AIX. You must stop and restart the Redirector for Keep-Alive to take effect.
- Timeout (minutes)
- Specify the number of minutes to wait before dropping an inactive Redirector connection. You must stop and restart the Redirector for the
Timeout value to take effect.
- IP Trace
- Type one or more IP addresses of clients you want to trace, separated by commas, to trace the number of bytes sent from the client to the host
and from the host to the client. The trace information is logged in NCoDServices.RAS.txt in the
private directory (for example,
C:\Program Files\HCL\ZIEForWeb\private or /usr/local/zieforweb/private).