Features at a Glance

Yes...the Georgia SoftWorks Windows NT Telnet Server includes a high performance proprietary client that may be installed at a many locations as you choose at no extra charge!

User Manual

Thank you for purchasing the Georgia SoftWorks Windows NT Telnet Server software. You will be pleased with the performance and robustness provided with this product. Ease of use will be a significant time saver when using the Georgia SoftWorks Windows NT Telnet Server software. Complicated keyboard sequences are not required to map to the actual keys you want to send. The Georgia SoftWorks Windows NT Telnet Server software was developed to meet a need in the market that allows users to operate in a fast, reliable and uncomplicated fashion.

Windows NT is transformed into a truly multi-user environment with the Georgia SoftWorks Windows NT Telnet Server software. Remote administration, full support for DOS Legacy applications, superior user control and Telnet Session Monitoring will allow you to utilize Windows NT as never before. True Client Side printing is available for a NT Telnet Server for the first time with the Georgia SoftWorks Windows NT Telnet Server.

Product Description

Our Telnet Server provides a level of robustness that is a cut above the competition. Industrial quality orphaned session detection and elimination including NTVDM's and attempted graceful termination of DOS legacy applications upon link and client PC failures are features pioneered by the Georgia SoftWorks Windows NT Telnet Server software.

Logon Scripting provides system administrators with unmatched control over user connections. One function of Logon Scripting allows the user to automatically enter specific applications upon connection. Logon Scripting can also restrict the user to only execute a specific application. Logon Scripting can do much more!

Server Software

The Georgia SoftWorks Windows NT Telnet Server is the software installed on your Windows NT computer. This software is responsible for establishing connections and spawning agent processes that manage each session. The Georgia SoftWorks Windows NT server software enforces the number of allowed simultaneous sessions.

Agent Process

A telnet session is created each time a connection is established. A connection is established when a user logs on to Windows NT system using a Telnet Client. For each session that is created the Georgia SoftWorks Windows NT Telnet Server software spawns an agent process. The agent process is responsible for managing and communicating with the user session. Screen optimizations are perf ormed by the agent process to facilitate faster data transfers. The capability of a configurable server side heartbeat timer exists for use by the agent process to help identify link or remote PC failures. In addition the configurable server side inactivity timer exists to help identify abandoned sessions so that they can be properly terminated and made available to other users.

Client Software

The Georgia SoftWorks Telnet Client is proprietary software that runs on remote PCs and utilizes advanced features offered in the server software. Other optimizations are included to enable this to be the fastest Windows NT Telnet software on the market.

The Client software contains a configurable heartbeat timer that notifies the agent process of its presence. This mechanism helps to identify link or remote PC failures.

It is recommended that the Georgia SoftWorks Windows NT Client software be used although it is not required. The Georgia SoftWorks Windows NT Telnet Server is RFC 854 compliant which allows any 3rd Party Telnet Client to be used. However many of the advanced features of the propriety client will be forfeited.

The Georgia SoftWorks Windows NT Telnet Client offers the Enhanced printing method as a component of True Client Side Printing. This allows users to print to their local printer even when connected across the Internet or RAS.

Installation

Installation is simple and quick. The same installation program installs the server software and the client software. The installation software will prompt you for a full or client only installation if on a Windows NT system and automatically install client software if on a Windows 95 system.

Server

Installation of the server software is simple. Run the setup.exe program. From Windows NT perform the following:

Run the setup.exe program.

1. The Welcome screen of the setup program is displayed and you are reminded and urged to exit all windows programs before continuing. You are also reminded that you must have administrative privileges to install this program. Click Continue.

2. The Installation options screen is displayed. The choices are Full Install or Install Client Only software. For Windows NT systems that you want clients to connect select Full Install using the Radio Buttons. The Full Install installs the Server Software and the Client software. Click Continue.

3. A screen is displayed indicating the directory that the Georgia SoftWorks Windows NT Telnet Server will be installed. The default is C:\Gs_tnet. You may change the installation directory at this time. Note: If you install on a drive other than the system drive and have NTFS(on the installation drive) then you must make sure that the system has full permissions to get to the installation directory and subdirectories. Click Continue.

4. The Setup Succeeded screen is displayed. The service has been installed and is automatically started.

Figure 1 - Telnet Server Program Group

Registration

Note: If you are installing the 30-day trial copy, you do not need to register the software. Skip this step.

To run the Georgia SoftWorks Windows NT Telnet Server you must first register the software. This entails just a few steps that involve obtaining the Product ID and providing this Identification to Georgia SoftWorks so a Serial Number can be generated. - NOTE: Read System Signature chapter at the end of manual.

To run the registration software either -

1. Click on the Registration Shortcut in the Telnet Server program group OR
2. Select the Start button on the task bar, select Programs, then Georgia SoftWorks Telnet Server for NT and then Registration.

Figure 2 - Registration: Customer Information

Once Georgia SoftWorks receives the information, we can generate a Serial Number on demand. We will reply back via Fax or email. You may close the registration program at this time.

1. When the Serial Number is provided Run the Registration Program again and enter the Serial Number. The easiest method to get the serial number is to highlight the returned Serial Number and copy (ctrl-c). Then position the mouse in the Serial Number field in the Registration Information box and paste (ctrl-v).
2. Click Register.

Figure 3 - Registration: Enter Serial Number

Figure 4 - Registration: Complete

Now the software is registered. You may now run the Georgia SoftWorks Windows NT Telnet Server. Note that you will be able to obtain Free Updates until the date specified.

Client

This is how you install the client software.

Installation of the Client software is simple. Run the setup.exe program. From Windows 95 or Windows NT perform the following:

Run the setup.exe program.

1. The Welcome screen of the setup program is displayed and you are reminded and urged to exit all windows programs before continuing. The setup program recognizes if it is a Windows NT system and prompts you for either a Full Install or a Client Only install. If this is a Windows NT system then select Client Only using the Radio Buttons. If this is a Windows 95 system then you are prompted for installation of the Georgia SoftWorks Windows NT Telnet Client. Click Continue.

2. A screen is displayed indicating the directory that the Georgia SoftWorks Windows NT Telnet Client will be installed. The default is C:\Gs_tnet. You may change the installation directory at this time. Click Continue.

4. The Setup Succeeded is displayed.

5. A "Program Group" is created. It contains one shortcut, the Georgia SoftWorks Telnet Client.

UN-Install

To uninstall the Georgia SoftWorks Windows NT Telnet Software follow these instructions.

1. Click the Start button on the Windows NT Task bar - go to Programs
2. Find the Georgia SoftWorks Telnet line - To the right select uninstall and follow the instructions. To reinstall the software you will need to re-register the software.

How to use the Georgia SoftWorks Windows NT Telnet Software

Georgia SoftWorks Client

Follow these instructions to open the Georgia SoftWorks Client window.

1. Click the Start button at the bottom left corner of your screen.
2. Click Programs
3. Move the mouse cursor to "Georgia SoftWorks Telnet Server" entry.
4. Click to the right where you see "GS Telnet Client"

At this point, the Client window is open and you will get the host prompt.

At this prompt, you should enter the hostname that you wish to connect. The hostname is the name your Windows NT computer is referenced by via TCP/IP. This can be a text string or an actual IP address.

Example:

The login ID must be a valid Windows NT login id.

Example:

This is the password associated with the Login ID. It will not be displayed when typed.

This is an optional field. If you do not wish to connect to a specific domain then you may simply press "<enter>". Otherwise type in the domain you want to connect. You may eliminate the domain prompt either by using command line. The Georgia SoftWorks Telnet Client Command line options are described next.

In addition to superior Perfect PC terminal emulation the Georgia SoftWorks Telnet Client has powerful command line options facilitating faster, easier and more flexible connections. Many of these options such as the Host, Username, Password and Domain can be used to eliminate prompting by the client or server when connecting to the Telnet Server.

The following optional command line parameters may be used

-uUsername

This specifies name of the user

-pPassword

This specifies password for the user. Use '.' if user has no password. Notice that this is a lowercase "p".

-dDomain

This specifies the domain of the user. Use '.' if you want to use default domain or no domain.

-hHostname

This specifies host name to connect to.

-HHeartbeatTime

This specifies our client side heartbeat. You need that parameter for the session cleanup!!

-PPort Number

Example-

Note: The last dot is for the default domain

3rd Party Clients

The Georgia SoftWorks Windows NT Telnet Server will work with any RFC 854 compliant 3rd party client. Please see the vendor's instructions for configuration of the 3rd party client.

The procedure for connecting with a 3rd party client is similar to connecting with the Georgia SoftWorks client (see above).

Upon connecting with a 3rd party client you will be prompted to select a terminal emulation mode. Choose the desired emulation by selecting the appropriate number. Be sure to set the 3rd party client emulation mode to the same emulation as the one selected on the server.

The terminal emulation options available are

• DEC VT-100
• DEC VT-220/320/420
• SCO Console
• AT386
• Wyse 50
• Wyse 60
• IBM 3101
• IBM 3151

Enter 0 for DEC VT-100 emulation, 1 for DEC VT-220/320/420, 2 for SCO Console emulation, 3 for AT386, 4 for Wyse 50, 5 for Wyse 60, 6 for IBM 3101, and 7 for IBM 3151 emulation.

If you do not want to be prompted for the emulation mode each time you log on using a 3^rd party client then you may set an environment variable on a per user basis using Logon Scripting (described later in the User Manual).

The environment variable for the terminal emulation is:

For example to select SCO Console emulation you would enter:

in the Logon Script for a particular user.

NOTE: No spaces are allowed when setting environment variables.

For example:

Graphic Characters

Third party clients do not always handle graphic characters and commands as expected. The Georgia SoftWorks Windows NT Telnet Server is flexible in providing options for handling graphic characters with 3^rd party clients. If you are unsure of which graphics mode to select the typical progression is the order that the selections are presented. The first works for all, the next is more specialized and so on. Feel free to experiment to determine the best graphics mode for your 3^rd party client. The graphics mode prompt indicates the recommended selection when SCO Console emulation is selected.

This simply replaces PC graphics characters with the "asterisk" character,

For VT emulation's the system converts the PC Graphic Characters to ACS and will temporally invoke Special Graphics character sets. PC Graphics without ACS equivalents will be converted to the "asterisk" character.

For SCO Console the system will inject appropriate escape sequences to display the graphic characters.

Pass PC Graphics characters without changes:.

This will pass any chars >= 0x80 without any changes.

Pass all characters from PC Screen without changes:.

This will pass all characters from the NT screen, your client software may have trouble with handling ASCII values for some of control characters like 0x08 (backspace).

If you do not want to be prompted for the graphics mode each time you log on using a 3^rd party client the you may set an environment variable on a per user basis using Logon Scripting. The environment variable for the graphics mode is:

For example to select star graphics character substitution you would enter:

in the Logon Script for a particular user.

NOTE: No spaces are allowed when setting environment variables. For example:

Many times programs are developed to work with monochrome monitors or terminals. In this situation you can choose between a color and monochrome presentation. After the graphics mode options are presented the color or monochrome options are presented. The prompt

Do you want ANSI Colors? [Y/N]:

If you want a Color presentation choose "Y". If you want a Monochrome presentation choose "N".

If you do not want to be prompted for the Color or Monochrome presentation each time you log on using a 3^rd party client the you may set an environment variable on a per user basis using Logon Scripting (described later in the User Manual).

The environment variable for the Color or Monochrome presentation is:

For example to select a color presentation you would enter:

in the Logon Script for a particular user.

And to select a monochrome presentation you would enter:

in the Logon Script for a particular user.

If the monochrome mode is selected the color mapping is performed as described below. For each character on the screen:

If background intensity is set then the blink attribute is set.

If foreground intensity is set then the bold attribute is set.

If the character is blue then the underscore attribute is set.

If background intensity is greater than foreground intensity then the inverse attribute is set as follows:

I = .3 * R + .6 * G + .1B

The intensity bit itself is not used in the above calculation. The attributes are additive.

This is how to change the registry key for the AltPrefix.

Note: (you must be on the Windows NT system that the Georgia SoftWorks Windows NT Telnet Server is installed. However you may connect to the Windows NT Registry from a remote location).

The key is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\AltPrefix

The new AltPrefix will take effect for all new sessions.

Third party clients will send escape sequences on certain occasions. For example when a function or arrow key is depressed a sequence of data is transmitted that starts with the escape character (0x1b). When the escape character is received, the server must determine if this escape is part of an escape sequence or simply an escape key. The server uses the ESC Delay value to determine how long to wait for the next character after an escape is received to consider it part of an escape sequence. If a character is not received within this time then the escape is considered to be a escape key, otherwise it is the start of an escape sequence.

The default value is 5 (500ms). You may want to increase this value if you see that escape sequences are not going through and being displayed on the screen rather than being interpreted. For example if you type F10 and see odd character starting with "]" or "[". This is most likely to happen with terminal servers or other slow links like RAS.

This is how to change the registry key for the Escape Delay.

Note: (you must be on the Windows NT system that the Georgia SoftWorks Windows NT Telnet Server is installed. However you may connect to the Windows NT Registry from a remote location).

The key is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\ESCDelay

Terminating a session

Type exit at the client window prompt followed by the ENTER key and the session will terminate and the window will clear and then close.

TTY Name

The Georgia SoftWorks Windows NT Telnet Server creates a tty name on a per session basis. This is available for viewing or use by customer created programs.

The environment variable created is:

And is set to /dev/ttypxxx, where xxx

represents the socket number (handle) for user's session.

Heartbeat - Specifying a Client Timeout value

To aid in the detection of failed links or failed remote PC's the Georgia SoftWorks Client software supports a Client Timeout value. The client will send a heartbeat to the server at specified time intervals. At installation, this value is set to 300 seconds. This can be changed using the shortcut properties.

If the server does not receive data from the client in the specified time, the connection is terminated. The data can be keyboard, or mouse input as well as the heartbeat. When keyboard or mouse data is transmitted, or when a heartbeat detected the server's timer is restarted.

The heartbeat time is specified as an optional command line argument in seconds.

specifies a heartbeat time of 30 minutes (1800 seconds = 30 minutes).

To change the Client Heartbeat

1. Single click on the GS Telnet Client Shortcut.
2. Right click, properties will be displayed, click on properties
3. Select the Shortcut Tab.
4. Change Target command line to reflect the new client side heartbeat timer. The default command string is c:\gs _tnet\gs_clnt.exe /H300. The H300 parameter is the heartbeat count in seconds. 300 is 5 minutes. You may change or delete this parameter.
5. Click on apply. The new heartbeat time interval takes effect when you log in.

Server Side Heartbeat Timer

The Server Side Heartbeat Timer is used for setting the frequency in seconds which to poll the 3^rd party client for presence. If the client is not present then Graceful Termination is initiated.

This timer is a registry key value and is in seconds. The key is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\ClntChkTimeout

The default value is 300. (That is five minutes)

You may disable this timer by setting it to 0xffffffff .

This is how to change the registry key for the Server Side Heartbeat Timer.

Note: (you must be on the Windows NT system that the Georgia SoftWorks Windows NT Telnet Server is installed. However you may connect to the Windows NT Registry from a remote location).

The new Server Side Heartbeat Timer will take effect for all new connections.

Server Side Inactivity Timer

If data (keyboard or mouse events) is not received from a client within the specified server side inactivity time then the client session is terminated. This feature is useful to ensure that an abandoned 3^rd party client session is terminated properly, releasing the telnet session for others to use. The Server Side Inactivity Timer is used only if the client side heartbeat is not used.

This timer is a registry key value and is in seconds. The key is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\InactivityTimeout

The default value is 0xffffffff that is -1. (That is disabled.)

This is how to change the registry key for the Server Side Inactivity Timer.

Note: (you must be on the Windows NT system that the Georgia SoftWorks Windows NT Telnet Server is installed. However you may connect to the Windows NT Registry from a remote location).

The new InactivityTimeout will take effect for all new connections that do not have a client heartbeat configured.

Logon Scripting - automatic execution of DOS applications and more

Logon Scripting is an advanced feature that allows the system administrator unmatched control over the user sessions. Associated with each User Login Id is a directory that will execute batch files upon connection. One of two optional batch files can be executed. One is named k_start.bat and the other is c_start.bat.

One use of these batch files is to allow automatic execution of a DOS application upon connection.

k_start.bat - This file runs upon connection and after its completion the user may get the system prompt. This batch file may set environment variables, establish network connections, run TSR's etc.

c_start.bat - This file runs upon connection and after its completion the session terminates. This can be used to restrict the user to a certain application. Even if the user executes a control-c or something similar this will not allow access other than what is specified in the batch file on the NT computer.

The batch files are set up by the system administrator for each user in the system. They must be in the directory

Of course InstallationPath and UserLoginID is replaced with the actual values.

If both k_start.bat and c_start.bat exist then only c_start.bat is executed. You may call k_start.bat from c_start.bat.

Here is an example script to allow automatic execution of a Physicians Office Application "medical.exe" upon connection for the user login id (nurse). The Physicians office application is in the directory c:\medical.

Step 1. Create directory

Step 2. Create batch file k_start.bat

Step 3. Add line to k_start.bat

Step 4. Save file and exit.

Now when the User login id "nurse" connects to the Windows NT system via telnet the application medical.exe will automatically be started. When the user exits the medical package, the Windows NT Command line prompt is displayed allowing other activity to occur.

Here is an example script that will allow the User login id (bill) only to execute the amortization program amortize.exe. The amortization program resided in the directory d:\amor

Step 1. Create directory

Step 2. Create batch file c_start.bat

Step 3. Add line to c_start.bat

Step 4. Save file and exit.

Now when the User Login ID "bill" connects to the Windows NT system via telnet the application amortize.exe will automatically be executed. When the user exits the amortization package, the telnet session will terminate.

Global Logon Scripting

There are situations where the system administrator may want to have the same logon script executed by all the users upon connection. Instead of creating a logon script for each and every user, a single logon script can be created that will be executed by all users upon connection. The Global Logon script operates in the same manner as a normal logon script except for the location of the script files. The system administrator may put the k_start.bat or c_start.bat file in the subdirectory SCRIPTS (under the install directory). The server looks first for k_start.bat or c_start.bat in user's subdirectory and will not use the global script if it can find user's script.

Here is an example script to allow automatic execution of a Physicians Office Application "medical.exe" upon connection for ALL users that do not have a c_start.bat or k_start.bat in their logon script directory. The Physicians office application is in the directory c:\medical.

Step 1. Create batch file k_start.bat in the SCRIPTS directory (under the install directory).

Step 2. Add line to k_start.bat

Step 3. Save file and exit.

Now when the any user (unless they have their own login script in their logon script directory) connects to the Windows NT system via telnet the application medical.exe will automatically be started. When the user exits the medical package, the Windows NT Command line prompt is displayed allowing other activity to occur.

Graceful Termination of DOS Applications

The Georgia SoftWorks Windows Telnet Server is unique in that in case of a link or remote PC failure we attempt to gracefully terminate the executing DOS application, therefore saving important data that may otherwise be lost. Many applications are terminated by sending a sequence of characters to the application such as ESC-ENTER. Applications may have specific sequences. We allow a termination string to be defined as an environment variable in the k_start.bat or c_start.bat file. When a session is to be terminated due the client heartbeat timer expiring or the server side inactivity timer expiring then the defined termination string will be sent to the associated application. Approximately 3 seconds later the session is terminated if still running.

The following control key designators are defined.

• shift-
• alt-
• ctrl-

The following special characters are defined.

• ESC
• ENTER
• F1
• F2 and so on through F12

Also a special operator is defined.

• Sleepxx

This special operator will pause the output to the shell for xx seconds. This gives the application time to process the input. This is very useful when saving files to disk and for applications that flush the keyboard buffer.

We will continue to use the amortization program from example 2. However, we will assume that a standard menu exists for the application. A File menu item exists that is invoked by alt-f. The list of items in the File menu list includes s for saving the work and alt-f for opening the file menu list again and then x for exiting the application. Next follows the ",e,x,i,t,ENTER" to gracefully close the shell.

Step 1. Create batch file c_start.bat

Step 2. Add this line to c_start.bat

d:\amor\amortize.exe

Step 3. Add this line to c_start.bat (note: there are no spaces in following the "=")

SET LRA_TERMINATION=alt-f,s,sleep5,alt-f,x,e,x,i,t,ENTER

Step 4. Save file and exit.

Now when the User ID "bill" connects to the Windows NT system via telnet the application amortize.exe will automatically be executed. If the session is terminated due to system timeouts the termination string alt-f,s,sleep5,alt-f,x will cause the following sequence of events to occur.

First Alt-f to be sent to the application (This opens the file menu).

Second s is send to the application (for saving the file).

Third, the Sleep5 causes 5-second pause to allow the application time to save the files,

Fourth alt-f to open the file menu list again,

Fifth an x is sent to the application to exit.

Finally ",e,x,i,t,ENTER" is send to the shell which terminates the session.

Other examples of termination string definitions are:

SET LRA_TERMINATION=alt-f,x,e,x,i,t,ENTER

SET LRA_TERMINATION=F2,alf-f,x,e,x,i,t,ENTER

SET LRA_TERMINATION=ESC,ENTER,e,x,i,t,ENTER

Client Scroll Bars

You may enable scroll bars on the Windows NT client window. This is accomplished by changing the buffer size for the DOS window. You must be careful that the application can handle a modified buffer size. Unpredictable display results will occur if this is not the case.

Monitoring other Telnet Sessions

Included with the Georgia SoftWorks Windows NT Telnet Server is a powerful administrative, development and training tool - the Session Monitor. The session monitor is a stand alone utility that allows users within a certain group to terminate other Telnet sessions or to connect to an existing Telnet session and observe the screen exactly as the client sees the screen. This connection only allows monitoring. You may use this utility as a local NT user or as a user connected via Telnet.

Session Monitoring Privileges.

To participate in Session Monitoring a user must belong to the group Gwtn Monitors. The system administrator must first create the group Gwtn Monitors. Next all users allowed to use the Session Monitor must be added to the group. You will have to restart the Windows NT server after creating the group and adding users. Windows NT does not instantaneously update the group membership after the user manager is closed.

Starting the Session Monitor

The name of the session monitor utility is gs_admin.exe and resides in the installation directory. When the session monitor is executed a window is opened that dynamically displays all Telnet sessions. For each session the Logon Id, the Logon time, the session id and the monitor id are displayed. The menu bar contains the items File and Sessions. The bottom right corner of the Session Monitor displays the number of Telnet Sessions that are currently active.

Monitoring other Telnet Sessions

To select a Telnet Session to monitor first highlight the session to monitor. This is accomplished either by moving the up/down arrow keys or clicking on the particular session. Once selected either depress <ENTER> or click the menu item Session to display the drop down item Monitor. You may now select Monitor.

You are now connected to the other telnet session, observing the screen activity exactly is appears to the other user. You may monitor only. No input is allowed to the other session. To end monitoring the other telnet session depress <ESC>. You are returned to the Session Monitor Screen.

Terminating other Telnet Sessions

To select a Telnet Session to terminate first highlight the session to terminate. This is accomplished either by moving the up/down arrow keys or clicking on the particular session. Once selected either depress <DEL> or click the menu item Session to display the drop down item Terminate. You may now select Terminate. You will be prompted to make sure that you want to terminate the session. Graceful Termination will take place upon terminating the session.

Exiting the Session Monitor

You may exit the Session Monitor either by the File then Exit Menu item or depressing the <ESC> key

Session Monitoring Uses.

There are many uses for session monitoring a few are listed.

• Quality Assurance - A supervisor can monitor data entry of employees.
• Training - A senior application user can remotely help a trainee understand and use a application.
• Debugging - A developer can remotely observe an application phenomenon that a user is describing.
• Administrative - A system administrator can ensure that users are using/setting up resources properly.
• Security - Administrator monitor users that are using telnet.
• Terminating Sessions that have been abandoned.
• Terminating Sessions that are connected to applications which are behaving abnormally etc.

Restrict access to the Telnet Server

Restrict user logon access via telnet setup.

If the system administrator decides to limit the users allowed to logon via telnet then the group Gwtn Users must be created. If this group exists then only members of this group will be allowed to logon via telnet. If this group does not exist then all users that can logon locally can log on via telnet. Once the group Gwtn Users is created, each user allowed to logon via telnet must be added to this group. You will have to restart the Windows NT server after creating the group and adding users. Windows NT does not instantaneously update the group membership after the user manager is closed.

Restrict connection based on Host IP address - Include or exclude

The system administrator may decide to limit the connections via telnet based on IP address. Remote access may be limited only to specific IP addresses. The system administrator may also restrict specific IP addresses from connecting via telnet.

You must create the file:

The file must reside in the Georgia SoftWorks Windows NT Telnet Server installation directory. The directive [EXCLUDE] indicates if the IP Addresses should be excluded from connection.

1. It is a text file
2. The # character is the comment character
3. [EXCLUDE] directive placed in the 1st line will force the interpretation as the exclusion file, otherwise only IP addresses listed are allowed.
4. Data after the IP address is ignored and therefore can be used for additional comment data.

Bill and Tom have machines that are in a public location and are not secure. The system administrator does not want to allow telnet access from those machines. However Bill and Tom have other machines that need telnet access to the server. This is how to set up the thosts file to exclude those particular machines.

Information needed:

IP address of Bill's machine: 198.68.20.21

IP address of Tom's machines: 198.68.22.25

[EXCLUDE]

# Here is the list of hosts that are not allowed to log in via telnet

198.68.20.21 Bob's machine

198.68.22.25 Tom's machine

Now lets look at the contents of the file.

The [EXCLUDE] directive specifies that all IP addresses listed in the thosts file are no allowed to connect via telnet.

The next line is a comment reminding the System Administrator that the following Host IP addresses will not be allowed to connect via telnet.

Next are the list of Host IP addresses to exclude. The list can be as long as you desire.

ACME Accounting has 3 remote locations. The machines at each location, however there may be dozens of different users that may be connecting from each machine at different times of the day. The system administrator only wants to allow telnet connections from the 3 remote locations.

However the ACME remote Location 3 office is temporally closed and is under remodeling. Therefor the system administrator want to easily comment remove them from the "allowed" list and quickly add them back as soon as the office reopens.

Information needed:

IP address of ACME accounting location 1 machine: 198.68.35.21

IP address of ACME accounting location 2 machine: 198.68.35.25

IP address of ACME accounting location 3 machine: 198.68.35.26

# Here is the list of hosts that are allowed to log in via telnet

#

198.68.35.21 ACME accounting location 1 machine

25. ACME accounting location 2 machine

#Lets not all location 3 until the office reopens.

#198.68.35.26 ACME accounting location 3 machine

#

True Client Side Printing - Printing the way you want it!

The Georgia SoftWorks Windows NT Telnet Server True Client Side Printing allows documents to be printed at locations that are easily accessible by each user. Traditionally, default printing using Telnet is always local to the server. This can be inconvenient to the user. Georgia SoftWorks overcomes the traditional problem by providing True Client Side Printing - printing the way you want it.

Any printer may be used on a per user basis. Georgia SoftWorks offers multiple printing methods for the telnet user that will address most printing requirements. They are

• Default - Works as if the telnet user is sitting at the Windows NT server.
• Enhanced - Printer output is sent to the telnet clients' local printer.
• Open - allows telnet user to configure the printing command used when printing.

Default Printing

Enhanced Printing

Enhanced printing is an advanced feature of the Georgia SoftWorks NT Telnet Client that allows the users client computers default printer to be the used when printing using telnet. The telnet user can override the default printer for their computer using command line arguments when initiating the client.

Open Printing

Setting up True Client Side Printing

There are two steps in setting up True Client Side Printing. Note: No setup is required for Default printing.

• Defining a Virtual Printer on the Server - This is the same for all printing methods
• Adding the Georgia SoftWorks printer redirection commands to a logon script. This is specific to the printing method chosen.

A Virtual Printer is defined that redirects the output from your application. The Georgia SoftWorks Telnet Server polls the Virtual Printer queue for new print jobs. When print jobs enter the Virtual Printer queue the originating user of the job is identified. Once the user is known the associated printer is referenced and the print job is redirected to that printer.

Create a virtual printer on the server.

In creating a Virtual Printer the key information is the Printer Name, the Share Name and the port.

1. Click the Start button at the bottom left corner of your screen.
2. Select Settings then printers.
3. Double click on Add Printer. (The add printer window opens).
4. Select My Computer and Click on Next
5. Select one of the unused lpt or com ports. Do NOT enable print pooling. Click Next.
6. From the Manufactures list select Generic
7. From the Printers select Generic/Text Only. Click Next
8. Name your printer GwtnPrinter. NOTE: This name is required. Click Next
9. Select Shared and name the printer GwtnPrinterShare. Click Next
10. After the printer is created, double click on the printer icon.
11. Pause the printer by selecting the menu item Printer and selecting Pause Printer. This printer must remain paused at all times. This printer can not be used by any other service except Georgia SoftWorks.

Now your virtual printer is created and is ready for use by telnet. However you must be sure to set the redirection commands in logon scripts.

Set virtual printer redirection commands in logon script.

For each user that is using the Georgia SoftWorks True Client Side Printing redirection commands must be added to their logon script. First the Virtual Printer must be associated with the printer device that the user wants to use. This is the device that the application will select when printing. This can be accomplished with the "net use" command. It is of the form:

Where

• lptx is the printer port that the application sends the printer output (typically lpt1 for Dos applications)
• \\servercomputername\GwtnPrinterShare is the specification for the virtual printer.

The next is an environment variable that indicates the True Client Printing method chosen. The environment variable is:

and valid values are:

The syntax is:

The Open print method allows the administrator to determine the print command used by Telnet when printing. There are unlimited applications for this printing method. Common uses involve printing to shared or network printers.

The Enhanced print method allows the default printer for a client system to be easily used by telnet. A common use for Enhanced printing is when connecting to the server across the Internet or via RAS.

The next environment variable that must be in the users logon script is dependent on the True Client Printing Method chosen.

Enhanced Print Method

I have salesmen that telnet to the server to get reports from a variety of locations. They carry laptops with portable printers and telnet to the server either through the Internet of via RAS. They need to get customer and shipping information printed. The sales program that they use prints to lpt3. How do they have printer output sent to their portable printers?

This is an excellent opportunity for the Georgia SoftWorks Enhanced True Client Printing Method.

The only requirement is that the Georgia SoftWorks Windows NT Telnet Client is being used. Of course the Virtual printer must be defined as described in the Virtual Printer section. The logon script for user SuperSalesMan needs to have the following commands:

Edit the users logon script k_start.bat and add the following commands:

NOTE: The above commands must appear in the logon script. It is not sufficient to set these at the command prompt nor in another batch file.

The portable printer must be connected to the laptop and be the default printer for that system.

When the salesman prints to lpt3 the output will appear on the default printer connected to the salesman's client computer. This same methodology can be used for as many users as you wish.

This is a variation of the previous example. Here the salesman has access to a color printer. Our salesmen carry laptops with portable printers and telnet to the server either through the Internet of via RAS. They need to get customer and shipping information printed. The sales program that they use prints to lpt3. A salesman is at the customer's office and wants to get a color printout of a sales report. The customer has a color printer handy. They connect the color printer and install the proper driver. It is not the default printer. How can the salesman print to the non-default color printer?

This is an excellent opportunity for the Georgia SoftWorks Enhanced True Client Printing Method with client override. A command line parameter when initiating the Georgia SoftWorks Windows NT Telnet Client allows printers other than the default printer to be used.

The Parameter is:

The only requirement is that the Georgia SoftWorks Windows NT Telnet Client is being used. Of course the Virtual printer must be defined as described in the Virtual Printer section. The logon script for user SuperSalesMan needs to have the commands described below. Edit the users logon script k_start.bat and add the following commands:

NOTE: The above commands must appear in the logon script. It is not sufficient to set these at the command prompt nor in another batch file.

Initiate the Client session as:

Gs_clnt.exe /rCustomerColorPrinter /H300

When the salesman prints to lpt3 for user SuperSalesMan the output will appear on the color printer.

Open Print Method

The Open Print Method is extremely powerful allowing the user to configure any valid printing command to be used when printing via telnet. The printing command and other parameters are configured by setting the print command environment variable. The environment variable is:

And the syntax of the command is:

set GWTN_LOCAL_PRINT_CMD=PrintCommand %s

Where

set GWTN_LOCAL_PRINT_CMD=print /d:\\clientcomputername\sharename %s

Note: the %s is typed exactly as it appears. Do not replace the %s with a file name. The system replaces the %s with the current NT-generated spool file as you print to your printing port. Note: You are not printing to that temporary file from your application - the system does this behind the scenes. Enhanced and Open printing methods allow you to print to the printer port as you normally would.

Where

set GWTN_LOCAL_PRINT_CMD=lpr -S Server -P printer %s

where

In my office I have a computer and a printer is connected to my computer. I am on the network and my printer is a shared printer. I use telnet to connect to the company server and I run accounting applications. The accounting application uses LPT1 as the printer port. How can I use the printer in my office when I print from the accounting applications?