The RTN3270E.DLL file provides complete TN3270E connectivity for BlueZone allowing connection to hosts, servers, and gateways that are TN3270E compliant. TN3270E is the enhanced version of TN3270, providing more SNA information to the client for improved operation. Optionally, Secure Sockets Layer security is available to insure privacy, message integrity and provide authentication.
TN3270E configuration consists of the following tabs: Connections, Device, Security, Certificate, Keep Alive, Trace, Firewall, Security Server and About. To quickly "jump" to anyone of these subjects, click the desired link.
NOTE The
TN3270E settings for the BlueZone Display emulator are identical to the
BlueZone Printer emulator with the exception of the Device
Tab. The
differences are shown in bold blue
type.
This dialog displays your host Connection List and contains buttons for creating new connections as well as editing, removing and sorting them.
TN3270 / TN3270E Connections ----
Connection List: This is a list of your configured hosts (if any). A total of 32 connections can be defined.
New Button: Used to create new host sessions. When clicked, the Define New Connection dialog will appear.
Connection Name: A unique name used to identify the collection of Connection settings.
Host Address: Specifies the computer name (in Internet format, known as DNS Name) or the IP address in either IPv4 or IPv6 format, of the TN3270E server.
LU Name: Specifies the name of the device to which to connect. This is optional.
SEE How
to Automatically Generate LU Names for more information.
TCP Port: Specifies the TCP port number to which to connect. The default is 23.
Backup Host: Specifies a second host connection if the first connection attempt fails.
Enable TN3270E: Enables the TN protocol extensions. The default is enabled.
Enable Extensions: Enables the TN3270E Function Extensions. These include support for SNA Contention Resolution, Send Data Indicator (SDI), Keyboard Restore Indicator (KRI), Bid, and Signal.
Connection Timer: Specifies the maximum amount of time (in seconds) to wait for the TN connection to complete.
Bypass Firewall: if enabled, individual connections can bypass the global firewall settings and connect directly to the host
Edit Button: Click here to edit an existing entry in the Connection List.
Remove Button: Click here to remove an existing entry in the Connection List.
Sort Button: Click here to sort the entire Connection List into alphabetical order.
Use Connection Name as Session Description: If enabled, the name that you gave to the active connection, will appear in the BlueZone Title bar, immediately after the session number. This feature is handy if you have multiple hosts defined, and you are not using the "Connections" drop down list, and you want to know the name of the current connection.
IBM Device ----
Device
Type ----
Selects the type of IBM terminal
or printer to emulate.
3278: Selects a 3278 (monochrome) display. (Display emulator only)
3279: Selects a 3279 (color) display. (Display emulator only)
3287: Selects a 3287 printer. (Printer emulator only)
Device
Model ---- (Display
emulator only)
Selects the default screen size of the emulated device to use when one
is not specified by the host system.
Model 2 (24x80): Selects a model 2 device with 24 rows and 80 columns.
Model 3 (32x80): Selects a model 3 device with 32 rows and 80 columns.
Model 4 (43x80): Selects a model 4 device with 43 rows and 80 columns.
Model 5 (27x132): Selects a model 5 device with 27 rows and 132 columns.
Dynamic: Selects dynamic device which can accept any model type.
Extended Attributes: Specifies whether the device supports SNA Extended Attributes (color & highlighting). (Display emulator only)
Override 3270 Emulation Model Type: Allows the Device Model specified here to override the Default Screen Model Type specified in the 3270 Emulation parameters. This is normally desirable unless the TN3270 server requires a terminal type model specification which differs from the model type configured in the host LU.
Security Options ----
All BlueZone emulator clients support the SSL v3 or TLS v1 protocol through the BlueZone Security Server or any SSL enabled telnet connection including IBM Communications Server for NT (SSL v3 only), OS/390, z/OS, and the iSeries V4R4 or higher. BlueZone clients may be pre configured for distribution with SSL/TLS enabled, eliminating the need for any end-user intervention in the installation or configuration process. The options for configuration include
Security Options ----
If you want to encrypt your session, choose one of the following encryption
methods from the drop down listbox. The
method is dictated by the secure Telnet host that you are connecting to.
None: Choosing None Indicates that no encryption is being used.
Implicit SSL/TLS: This method negotiates a secure connection to the host first, then negotiates the Telnet connection.
NOTE For
users of BlueZone prior to version 5.1, when SSL/TLS encryption was enabled,
you were using Implicit SSL/TLS, even though the dialog did not expressly
state Implicit SSL/TLS encryption.
SSL
Version ----
Specifies which version of the SSL protocol should be used.
SSL v3: (Default)- Specifies that SSL version 3 should be used.
TLS v1: Specifies that TLS version 1 should be used.
NOTE SSL
v3 and TLS v1 are nearly
identical. TLS
v1 is preferred.
Invalid
Certificates ----
Specifies how to handle an invalid server certificate. Options include:
Always Reject: Specifies that an invalid server certificate should always be rejected.
Ask Before Accepting: (Default) Specifies that the user should be asked whether to accept an invalid server certificate.
Always Accept: Specifies that an invalid server certificate should always be accepted.
Preferred Cipher Suite: Specifies a specific SSL/TLS cipher suite (encryption algorithm) to use. To allow the client and server to negotiate the cipher suite, select "None".
NOTE This
product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/).
Client Certificate ----
These parameters specify the type of Client Certificate to use if any. Enable Secure Sockets Layer on the Security tab must be enabled in order for Client Certificate support to be active.
No Client Certificate - Specifies that a client certificate should not be presented.
Client Certificate in Disk File - Specifies that a client certificate should be presented.
Certificate File - Specifies the path to the Certificate File.
View - Use the View button to view the certificate.
Browse - Use the Browse button to locate the Certificate File.
Private Key File - Specifies the path to the Private Key File.
Browse - Use the browse button locate the Private Key File.
Client Certificate in Certificate Store - Specifies that a client certificate should be presented that is located in the Certificate Store.
Common Name - Specifies the path to the Common Name File.
View - Use the View button to view the certificate.
Browse - Use the browse button to display a list of certificates in the Certificate Store.
Client Certificate in Certificate on Smart Card - Specifies that a client certificate stored on a Smart Card should be presented.
Root Certificate ----
These parameters specify the which Root Certificate store to use. The one provided by OpenSSL, or the one that is provided by Windows.
Use OpenSSL Root Certifcates - (Default) If selected, the Root Certificates provided by OpenSSL will be used.
Use Windows Root Certificates - If selected, BlueZone will look will look for a file called rootcerts.pem in the End User's bluezone\certs directory. If it doesn't exist, it will automatically export the root certificates from Windows and store them there, giving a message such as ''109 root certificates were exported.''
Update Root Certificates - This button is used to manually export the certificates. If you connect and are presented with an untrusted host root certificate, and check the box to add it to the trusted list, it will import it into the Windows root store (which may produce a Windows message asking for confirmation), and then export the root store again to disk producing a message such as ''109 root certificates were exported.'' When this is performed one time, subsequent connections should connect without messages.
NOTE This
product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/).
Timer Options ----
These parameters specify whether the client should send keep-alive messages to the server to keep the TN3270E session active.
Disable: Disables keep-alive messages. (Default)
Use NOP: Uses the Telnet NOP (No Op) for keep-alive messages.
Use Timing Mark: Uses the Telnet Timing Mark (TM) for keep-alive messages.
Timer Value (Minutes): Specifies the time interval (in minutes) for sending keep-alive messages.
These parameters specify the interfaces to be traced and the file name to which the trace file will be written. The trace files are in ASCII text format and may be viewed with Note Pad or Word Pad.
STEP-BY-STEP How to Capture
a BlueZone Trace
Trace Options ----
Trace Sockets Interface: Traces the data as it passes through the Winsock interface from the network connection.
Trace RUI Interface: Traces the data as it passes between the TN3270E driver and the BlueZone terminal session.
Trace SSL Connection: Traces the data as it passes through the Secure Sockets Layer component of the TN3270E driver.
Trace File: Specifies the file name to which the trace file will be written.
Browse: Displays a dialog used to select the directory and file name. BlueZone provides a Traces directory in the BlueZone installation directory.
CAUTION! This
must be a valid path or the trace feature will not work.
Trace Viewer: Specifies the program that will be used to read the trace file after it has been captured and written.
Browse: Displays a dialog used to select the directory and file name.
Start Trace: Used to manually start the trace.
Stop Trace: Used to stop the trace.
View Trace: Used to view the trace. BlueZone will automatically use the Trace Viewer program specified above.
The Firewall tab allows the configuration of Firewall and Proxy Server sign on systems.
Firewall Options ----
Connect Through Firewall or Proxy Server: Check to enable this feature.
Firewall Type: Choose the Firewall Type from the drop down listbox:
SOCKS4 Proxy
SOCKS4A Proxy
SOCKS5 Proxy
NVT Proxy or Firewall
HTTP Tunneling Proxy
Firewall Address: Enter the IP address of the Firewall.
Port: Enter the Port number used by the Firewall.
Timeout: Enter the appropriate Time out value.
User Name: Enter the appropriate User Name.
Password: Enter the appropriate Password.
Domain: Enter the appropriate Domain.
NOTE If
you have chosen NVT Proxy or Firewall,
then you will need to provide the following additional information:
Host Name Prompt: Enter Firewall of network prompts BlueZone should look for.
User Name Prompt: Enter the User Name that the Firewall is expecting.
Password Prompt: Enter the Password that the Firewall is expecting.
Connected Prompt: Enter the appropriate Connected message that the Firewall transmits.
The Security Server tab is used to configure BlueZone to use the BlueZone Server as a Proxy Server to multiple hosts. This feature enables you to support connecting to multiple "back end" hosts through a single port in the BlueZone Security Server while using HTTPS tunneling in BlueZone.
Security Server Options ----
Use Security Server to proxy to Multiple Hosts: Enable
Proxy Type: Choose the desired Proxy Type from the listbox.
Security Server Address: Enter the IP address of the Security Server.
Port: Enter the Port being used by the Security Server for these connections.
Timeout: The time (in seconds) after which, if a prompt from the Firewall has not been received, BlueZone will assume that the Firewall has been traversed and proceed with the next stage of the connection process. This is required for Firewalls which authenticate a user once but then do not re-authenticate on subsequent connections within a certain time period.
This tab is used to display information about the encryption technology used by BlueZone.
Related Topics:
Establish a Secure Host Session