QTerm 7.0

The 7.0 version of QTerm brings a new look and easily accessible function panels which can be permanently displayed (pinned) or can be automatically hidden and only displayed when moused over. Mutiple frame windows are also supported with one or more terminal windows in each frame. This allows you to easily take advantage of multiple monitors.

If you are interested in trying out the new version please click here to download the software

Click New to close.

New

 

AccessClient

Description

The AccessClient provides a secure client interface for host access. With QTerm on your desktop you already have an encryption capable client and this facility can now be made available to 3rd party products without native encryption support.

Client emulators connect to the AccessClient running on their desktop which in turn connects to a remote AccessServer over a TCP/IP connection. This relay allows the AccessClient to implement security, client verification and extra functionality transparent to both the client and the host, which is especially important when opening up enterprise host access from the internet.

The AccessClient runs almost invisibly; just an icon in the system tray provides access to the visual management interface with easy to use configuration and status monitoring.

Requirements

The AccessClient is a Win32 application and runs on a 32bit Windows platform.

Visual Interface

The AccessClient user interface is a tabbed dialog with three window panes:

  1. Properties
  2. Status
  3. Logging

The properties page allows you to configure up to 8 host connections.  The status pane displays a list of the sessions with status and statistics  The log pane simply displays events as they happen.

Note: the log shows user names with and without a -H suffix (eg User001 and User001-H).  The suffix indicates the host connection side of the session.

Installation and Configuration

Installation is simply a matter of running the SETUP.EXE program

Assuming that your TCP/IP is properly connected and configured all that remains is to configure each connection to the AccessClient.  There are basically two sides to each connection: a listening port to which your client side emulator will connect and a destination host which is typically the address of a remote AccessServer.

Remember that the IP addresses and port numbers must match.  Also remember to turn on security only if the remote end is also configured for secure sessions. 

shared border