Georgia SoftWorks
Windows NT Telnet Server Software User Manual
User Manual
Georgia SoftWorks
Georgia SoftWorks Windows NT Telnet Server
Copyright
ã 1997, Georgia SoftWorks, All Rights ReservedPublic Square
33 Hwy 9 South • PO Box 729
Dawsonville Georgia 30534
Telephone 706.265.1018 • Fax 706.265.1020
http://www.georgiasoftworks.com
Copyright © Georgia SoftWorks, 1997 All Rights Reserved.
User's Manual, Version 5.11, Nov 3, 1998
Microsoft, Windows, Windows NT, Windows 95 are trademarks of Microsoft Corporation.
THIS PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
LICENSOR MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED, ORAL OR WRITTEN, REGARDING THE PROGRAM OR DOCUMENTATION AND HEREBY EXPRESSLY DISCLAIMS ALL OTHER EXPRESS OR IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LICENSOR DOES NOT WARRANT THE PROGRAM WILL MEET YOUR REQUIREMENTS OR THAT ITS OPERATION WILL BE UNITERRUPTED OR ERROR FREE.
IN NO EVENT WILL GEORGIA SOFTWORKS BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE SUCH PROGRAMS.
COPYING:
WHILE YOU ARE PERMITTED TO MAKE BACKUP COPIES OF THE SOFTWARE FOR YOU OWN USE AND PROTECTION, YOU ARE NOT PERMITTED TO MAKE COPIES FOR THE USE OF ANYONE ELSE.
LICENSE:
YOU ARE LICENSED FOR A SPECIFIC NUMBER OF CONCURRENT OR SIMULTANEOUS CONNECTIONS TO A SINGLE WINDOWS NT SYSTEM. THE NUMBER IS SPECIFICED IN YOUR PURCHASE AGREEMENT. ANY ATTEMPT TO INCREASE THE NUMBER OF SIMULTANEOUS OR CONCURRENT CONNECTIONS EITHER INTENTIONAL OR UNINTENTIONAL IS IN VIOLATION OF THIS AGREEMENT. THE GEORGIA SOFTWORKS WINDOWS NT TELNET SERVER SOFTWARE MAY BE INSTALLED ON A SINGLE WINDOWS NT SYSTEM.
Table of Contents
Features at a Glance
*Product Description
*Server Software
*Agent Process
*Client Software
*Installation
*Server
*Registration
*How to Register the Software
*Client
*UN-Install
*How to use the Georgia SoftWorks Windows NT Telnet Software
*Georgia SoftWorks Client
*Host
*Login ID
*Password
*Domain Name
*Georgia SoftWorks Telnet Client Command line options
*Example - Georgia SoftWorks Telnet Client Command Line Options
*Terminating a session
*Connecting using a 3rd Party Client
*Feature Packs
*Security Pack
*Encrypted Data Stream
*Data Stream Encryption Client Parameters
*Data Stream Encryption Server Environment variable.
*Enable Encryption Server Registry variable
*Proper Operating System DLL’s
*Encrypted Logon Sequence
*Connection Restrictions - Restrict access based on User ID.
*Connection Restrictions - IP Address: Restrict based on Host IP Address
*How to set up Host IP Address Restriction.
*Example - IP Restriction: restrict certain Hosts from connecting via telnet.
*Example - Restriction: allow only specific Hosts to connect via telnet.
*Restrict users to a specific application
*Expired Password Handling
*Integrated with Windows NT Security
*Performance Pack
*Fast, Fast, Fast
*Compression for slow link speeds
*Slow link and Internet optimizations
*Proprietary performance algorithms and code optimizations.
*Failure Detection/Recovery Pack
*Complete Session Cleanup
*Complete NTVDM Cleanup
*Server Side Inactivity Timer
*Server Side Heartbeat Timer
*Client Side Heartbeat Timer
*Example - Set the Georgia SoftWorks telnet client side heartbeat
*Graceful Termination of DOS Applications
*Example - Graceful termination: Amortization program - link failure.
*Termination Scripts
*Example - Termination Script: Cleanup.bat file unmapping the "f" network drive
*Legacy Pack
*Mouse
*DOS Character Mode Color Graphics
*Function Keys
*Special Characters
*Screen Sizes other than 25 x 80
*Alt Key Support for all emulations
*Emulation Pack
*3rd Party Clients
*Terminal Emulation
*Graphic Characters
*Color or Monochrome Presentations
*Color Mapping for Monochrome
*Alt Keys
*ESC Delay
*Power Features Pack
*Monitoring other Telnet Sessions
*Session Monitoring Privileges.
*Starting the Session Monitor
*Monitoring other Telnet Sessions
*Terminating other Telnet Sessions
*Exiting the Session Monitor
*Session Monitoring Uses.
*Logon Scripting - automatic execution of DOS applications and more
*Example - Logon Scripting: Automatic Execution of a program upon connection
*Example - Logon Scripting: User restricted to execute only a specific program.
*Global Logon Scripting
*Example - Global Logon Scripting: Automatic Execution of a program upon connection by ALL users
*Programmatic Access to the Telnet Server
*True Client Side Printing - Printing the way you want it!
*Default Printing
*Enhanced Printing
*Open Printing
*Setting up True Client Side Printing
*Create a virtual printer on the server.
*Set virtual printer redirection commands in logon script.
*Enhanced Print Method
*Example - Enhanced Printing: Printing to my local printer when connected across the Internet or RAS
*Example - Enhanced Printing: Multiple Client SIDE Printers
*Example - Enhanced Printing: Overide
*Open Print Method
*Example - Open Printing: Print to a client computer’s shared printer
*Example - Open Printing: Print to a Network Printer
*Compatibility Pack
*RF Wireless handhelds and the Georgia SoftWorks NT Telnet Server:
*Utility Pack
*Change Password command line utility
*Example - Utilities: Change Password
*Reboot NT computer command line utility.
*Example - Utilities: Reboot NT System
*Special Bell Processing.
*TTY Name
*Client Scroll Bars
*Setting a default domain
*A few Common Questions
*Can I use a port other than port 23 for the Telnet Server
*Can I telnet to the Telnet server and then telnet to another server?
*I can't logon from Telnet, what should I do?
*I am the Administrator but gs_admin.exe says I do not have administrative privileges?
*I want to set the background color on the client Window and make it distinct from the standard MSDOS Windows?
*I want to change the size of the window. The client is set to 80x40 but when it connects to the server it reverts back to 80x25.
*How do I eliminate prompting for the various settings when using 3rd party clients?
*Can I eliminate prompting for the Host, UserID and Password?
*Can I eliminate prompting for the Domain?
*Can I connect from older systems with DOS or Windows 3.1
*Can I have the user deposited into a specific directory upon connection?
*Is there any way to get the bell to sound on the client?
*Can I start and stop services when connected via telnet?
*Can I configure user information when connected via telnet?
*Discussion: Orphaned NTVDM's and Windows NT Telnet Servers
*Discussion: PIFs and your MS-DOS application's Performance
*Environment Variables Set by the User
*Environment Variables Set by the Telnet Server
*Registry Variables
*System Signature - IMPORTANT PLEASE READ
*Technical Support
*
Table of Figures
Figure 1 - Telnet Server Program Group
*Figure 2 - Registration: Customer Information
*Figure 3 - Registration: Enter Serial Number
*Figure 4 - Registration: Complete
*Figure 5 – True Client Side Printing: Printing across the Internet or RAS
*Figure 6 – True Client Side Printing: Using Multiple Client Side Printers per User
*Figure 7 – True Client Side Printing: Enhanced Printing Override
*Figure 8 – True Client Side Printing: Open Print Method
*
Table of Tables
Table 1 - Security Pack
*Table 2 - Speed Pack
*Table 3 - Failure/Recovery Pack
*Table 4 - Legacy Pack
*Table 5 - Emulation Pack
*Table 6 - Alt Prefix values
*Table 7 - Power Features Pack
*Table 8 - Compatibility Pack
*Table 9 - Utility Pack
*
Table of Examples
Example - Georgia SoftWorks Telnet Client Command Line Options
*Example - IP Restriction: restrict certain Hosts from connecting via telnet.
*Example - Restriction: allow only specific Hosts to connect via telnet.
*Example - Set the Georgia SoftWorks telnet client side heartbeat
*Example - Graceful termination: Amortization program - link failure.
*Example - Termination Script: Cleanup.bat file unmapping the "f" network drive
*Example - Logon Scripting: Automatic Execution of a program upon connection
*Example - Logon Scripting: User restricted to execute only a specific program.
*Example - Global Logon Scripting: Automatic Execution of a program upon connection by ALL users
*Example - Enhanced Printing: Printing to my local printer when connected across the Internet or RAS
*Example - Enhanced Printing: Multiple Client SIDE Printers
*Example - Enhanced Printing: Overide
*Example - Open Printing: Print to a client computer’s shared printer
*Example - Open Printing: Print to a Network Printer
*Example - Utilities: Change Password
*Example - Utilities: Reboot NT System
*Typographic Conventions
Italics
: are used to emphasize certain words, especially new terms or phrases when they are introduced.Initial Caps Bold: Words that appear in initial caps boldface represent menu options, buttons, icons or any object that you may click.
Courier
: This font represents anything you must type."<enter>" This represents the enter key.
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!
Do it right or don't do it at all! - Expected features where other fall short |
||
Full Support |
· DOS Legacy applications· DOS Character Mode ColorGraphics · Function Keys, SpecialCharacters · Mouse |
· Advanced Performance Features - fast - fast -fast !· Keep Network Traffic and ISDN cost down· Automatic support for Screen sizes otherthan 25 x 80 · Alt Key support for all Emulation's |
Administrators -Take charge of your system with unmatched control over user sessions. |
|
Logon/ Termination Scripting |
· Allow a user to automatically enter a specific application upon connection.· Optionally restrict a user to enter only a specific application upon connection.· Run TSR's and set Environment variables upon connection.· Establish network connections and more upon connection.· Termination scripting – Disconnect Network drives, etc. upon termination.
|
Don't corrupt that Database! Send commands to the application to save data and exit properly. |
|
Graceful Termination |
· Upon abnormal termination of client.· On Link or Remote Computer failure. |
Robustness - Multiple advanced failure detection methods. |
|
Client Heartbeat |
· Specify optional client heartbeat interval. |
Server Side Heartbeat |
· Specify optional server side heartbeat to check for client presence. |
Server Side Inactivity |
· Specify optional server side inactivity timer to check for abandoned clients. |
Flexibility - Don't forget those 3rd party telnet clients, Network Terminals and Terminal Servers and Developers! |
|
RFC 854 Compliant |
· Compatible with 3rd party Telnet clients such as TinyTerm, PowerTerm,NetTerm, Unix etc! |
Terminal Emulation's |
· SCO Console, DEC VT100, DEC VT220, DEC VT320, DEC VT420· AT386, Wyse 50, Wyse 60, IBM 3101, IBM 3151 |
Developers |
· Programmatic Access to the Server; Remote debugging via OutputDebugStringand MFC TRACE MACROS! |
Connect to existing telnet session and transparently monitor all screen activity |
||
Session Monitoring |
· Security - Monitor all telnet users on the NT system· Quality Assurance - Remotely Monitor data entry by employees· Training - Senior application users remotely help trainee's· Debugging - Developers remotely observe phenomenon described by users· Administration - Ensure that users are using/setting up resources properly· Terminate other telnet sessions |
Don't let your NT Server grind to a halt because of a link or client failure! |
|
Industrial Quality Session Cleanup |
· Advanced Detection of Orphaned NTVDM's.· Complete Elimination of Orphaned NTVDM's. Even during abnormalterminations. |
Who else does it like the Georgia SoftWorks Windows NT Telnet Server |
|
Support, Support & more Support! |
· Color support with 3rd Party Clients· Support for Clients that have non-color (monochrome only) monitors.· Support of programs that dynamically resize the windows(example: Norton Commander). · Support for graphics characters for 3rd party terminals. BOX and otherspecial characters. (example: Microsoft Edit) · Wide range of terminal emulation's, graphics modes and graphics translationsoptions to support dumb terminals and 3rd party clients. · The Georgia SoftWorks Windows NT Telnet Client excels in speedand performance! |
True Client Side Printing - Printing the way you want it – Support for multiple printers per user! |
|
Print to the most convenient printers |
· Default - As if you are sitting at the server.· Enhanced - Print locally when connected across the internet or using RAS.· Open - All valid print commands are now available to Telnet!
|
User Manual
Speed, Robustness and Ease of Use define the character of the Georgia SoftWorks Windows NT Server software.
hank 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, Telnet Session Monitoring and Data Stream Encryption will allow you to utilize Windows NT as never before. True Client Side printing is also available for a NT Telnet Server for the first time with the Georgia SoftWorks Windows NT Telnet Server.
The Georgia SoftWorks Windows NT Telnet Server is an industrial quality NT Telnet server designed and built for the most demanding industrial and commercial applications
.he Georgia SoftWorks Windows NT Telnet Server and Client software is the fastest and most robust Windows NT Telnet Software on the market. Full support for DOS Legacy applications including DOS character mode graphics, function keys, mouse and special characters allows you to work in a local mode when at a remote location.
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 unique features to 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!
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.
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 performed 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.
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.
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.
The HostName or IP address is displayed in the title bar of the Georgia SoftWorks Telnet Client to provide an easy method of identifying to which host you are connected.
Many command line parameters are provided to enhance the convenience and power of the client. Please see page
* for detailed descriptions of these parameters.
nstallation 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/98 system.
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.
5. A "Program Group" is created (Figure 1). It will contain 3 shortcuts. One is the Georgia SoftWorks Telnet Client, the second is the Registration shortcut, the third is the uninstall program.
Figure 1 - Telnet Server Program Group
NOTE: TCP/IP must be installed and operational. TCP/IP comes as part of Windows NT.
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 -
Note: The Product Information Name and Version must contain valid data or it will not generate a correct Product ID. If the name and version contain questions marks (????) then it is an indication that the Registration software was not invoked as described above and does not contain valid data.
The registration screen is displayed. The Registration software automatically fills in the Product Information fields. Complete the Customer Information fields as shown in Figure 2.
Figure 2 - Registration: Customer Information
a. Print the information and Fax it to Georgia SoftWorks
b. Save the information to a file and email it to Georgia SoftWorks - Preferred method.
Please save (using the Save to file button on the registration screen) this information to a file and email to Georgia SoftWorks - registration@georgiasoftworks.com
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.
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.
IMPORTANT: READ SYSTEM SIGNATURE CHAPTER AT END OF MANUAL (PAGE
*).This is how you install the client software.
Installation of the Client software is simple. Run the setup.exe program. From Windows 95/98 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/98 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.
To uninstall the Georgia SoftWorks Windows NT Telnet Software follow these instructions.
How to use the Georgia SoftWorks Windows NT Telnet Software
Follow these instructions to open the Georgia SoftWorks Client window.
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. This name will appear in the client windows title bar.
Example:
Host:
SolomanOr
(if you know the IP address you can enter the address)Host: 100.100.100.101
Or just press enter to connect to the local host for testing.
The login ID must be a valid Windows NT login id.
Example:
Login:
JohnSmithThis 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 options or by setting a default domain on the NT Server. To set the default domain for all users follow the instructions on page
*. The Georgia SoftWorks Telnet Client Command line options are described next.Georgia SoftWorks Telnet Client Command line options
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!!
-PPortNumber
This specifies the port number to use for telnet. This port must also be set on the server in the services file. Notice this is an uppercase "P".
-c
This specifies that the client uses Encryption. This option works only in conjunction with corresponding settings on the server. See page
* on setting up encryption.-r1=printername
-r2=printername
-r3=printername
This specifies Printer1, Printer 2 or Printer 3 for Enhanced Mode client side printing. Please see page
* for more information.Following is an example for specifying client command line parameters. In most cases the shortcut will be modified to provide the parameters in a transparent manner to the user.
Example - Georgia SoftWorks Telnet Client Command Line Options
Host
: solomanHeartbeat: 150
UserName: johndoe
Password: fastest
Domain: Use the default domain.
Encryption: Yes
gs_clnt -H150 -hsoloman -ujohndoe -c -pfastest -d
.Note: The last dot is for the default domain
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.
Connecting using a 3rd Party Client
Please see the section on Emulation’s for descriptions in connecting to the Georgia SoftWorks Telnet Server for Windows NT using 3rd party clients (page
*.).
The Georgia SoftWorks Windows Telnet Server is packed with features. The totally of the features are geared toward industrial and commercial application. The features logically group into units called packs.
All feature packs are included with the Georgia SoftWorks Telnet Server at no extra cost!
Security Pack – (see page
*)The Security Pack provides the system administrator with confidence that the NT System and the data transferred remains secure. Encryption, access and usage restrictions are among security features implemented.
Performance Pack – (see page
*)Advanced proprietary algorithms, optimizations and compressions provide for the fastest Telnet Server for Windows NT on the market.
Failure Detection/Recovery Pack – (see page
*)Industrial and commercial applications demand sophisticated failure detection and recovery methods. Georgia SoftWorks recognized the requirement and has unequaled capabilities in this area.
Legacy Pack – (see page
*)Proper operation with Legacy applications is the foundation of a quality telnet server. The Georgia SoftWorks Telnet Server for Windows NT will meet or exceed all expectations with respect to running legacy applications.
Emulation Pack – (see page
*)The Emulation Pack provides all the popular emulation’s’ required by most 3rd party clients. Not only are the emulation’s provided but they are implemented correctly.
Power Features Pack – (see page
*)The Georgia SoftWorks Telnet Server provides the most powerful, needed and useful features on the market.
Compatibility Pack – (see page
*)RFC 854 compliance provides access from other platforms allowing the Telnet Server to be utilized by a variety of users.
Utility Pack – (see page
*)Several utilities are provided for the telnet user to simplify and ease the use of telnet.
Georgia SoftWorks provides unmatched security when using our Telnet Sever for Windows NT. It is the only Telnet server that offers complete Data Stream Encryption. The Georgia SoftWorks Telnet server has been submitted to the United States Department of Commence and has obtained the proper license exceptions so it can be legally exported around the world.
Data Stream encryption can be enabled on a global or a per user basis with undetectable performance loss. This is useful if users are running accounting, banking, medical or other applications that contain sensitive data.
Logon only encryption may also be employed. This protects User Ids, Passwords and other logon data.
The Georgia SoftWorks Windows NT Telnet Server is integrated with Windows NT Security. All Windows NT security concepts apply. The Georgia SoftWorks Windows NT Telnet server allows the system administrator to optionally restrict telnet access based on User ID or IP address. These are additional security measures above the normal Windows NT security. The system administrator can specify the users that are allowed to logon via telnet
Security Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Encrypted Data Stream |
Yes |
Yes |
No |
Encrypted Logon Session |
Yes |
Yes |
No |
Connection Restrictions - User Id |
Yes |
Yes |
Yes |
Connection Restrictions - IP Address |
Yes |
Yes |
Yes |
Restrict to a specific application |
Yes |
Yes |
Yes |
Expired Password Handling |
N/A |
Yes |
Yes |
Integrated with NT Security |
N/A |
Yes |
Yes |
|
|
|
|
Encryption of the Data Stream for Telnet on NT is another feature pioneered by Georgia SoftWorks. Complete Data Stream encryption is available on a global or per user basis when using the Georgia SoftWorks Telnet Client. For encryption to work both the sending and receiving ends of the data must know to encrypt and decrypt the data. Since third party clients would not be aware of encryption or decryption, data stream encryption is only available with the Georgia SoftWorks Telnet Client.
The Setup for Data Stream Encryption requires:
Data Stream Encryption Client Parameters
The parameter
-c should be passed when invoking the Georgia SoftWorks Windows NT Telnet Client. This can be passed from the command line via the following command:gs_clnt.exe -c
The shortcut may be modified to pass Data Stream Encryption parameter.
Data Stream Encryption Server Environment variable.
An environment variable must be set on either a Global or Per User basis to activate Data Stream Encryption.
The environment variable for the complete data stream encryption is:
gwtn_encrypt_session
in the Logon Script for a particular user (or the Global Logon Script for all users.).
NOTE: No spaces are allowed when setting environment variables.
For example: To Activate Data Stream Encryption the following line should be present in the logon script.
set gwtn_encrypt_session=1 is correct
set gwtn_encrypt_session = 1 is not correct
For example: To De-activate Data Stream Encryption the following line should be present in the logon script.
set gwtn_encrypt_session=0 is correct
Enable Encryption Server Registry variable
The variable
EnableEncryption is a registry key value. This Registry key enables or disables the ability to activate Encryption. If it is disabled then all encryption environment variables are ignored. Also the client command line parameter must not be used when the registry value is disable. The key is:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\EnableEncryption
The default value is 0(That is disabled.) The value 1 enables the ability to use Encryption. The value 0 disables the ability to use encryption.
This is how to change the registry key for Encryption.
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 EnableEncryption value will take effect for all new connections.
Encryption requires specific operating system Dll’s (that are present on most systems) to exist to run the telnet client and server.
These files come with Windows NT 4.0 and are included in Microsoft Internet Explorer Version 3.0 and above. If you do not have these system files encryption will not operate.
If you have Windows 95 then you must have at least OEM release 2 or Internet Explorer 3.0 or later. Windows 98 has all the required files.
You may choose to only encrypt the logon sequence when using the Georgia SoftWorks Telnet Client. This entails the same steps as described with Complete Data Stream encryption except there is no environment variables to set in the logon scripts.
Connection Restrictions - Restrict access based on User ID.
The system administrator may optionally restrict connections via telnet based upon the user id. This is useful when you have a defined set of users that you would allow to access the NT Server via telnet. If the system administrator decides to limit the users allowed to logon via telnet then the local 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.
Connection Restrictions - IP Address: Restrict based on Host IP Address
The system administrator may optionally restrict connections via telnet based upon the Host 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.
Restrictions based on IP address are enforced when the file
thosts exists. The IP addresses of interest are listed in the thosts file. In short, only IP addresses listed in the thosts file are allowed to connect via telnet. The provision also exists to exclude specific IP addresses from connecting via telnet. A keyword [Exclude] is used that indicates all IP Addresses listed in the file should be excluded from logon via telnet.How to set up Host IP Address Restriction.
You must create the file:
thosts
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.
NOTE: The System account must have permission to read the
thosts file.The rules are simple for setting up the
thosts file.Following are example
thosts files.Example - IP Restriction: restrict certain Hosts from connecting via telnet.
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
Edit the file
thosts and add the following lines.[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.
Example - Restriction: allow only specific Hosts to connect via telnet.
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
Edit the file
thosts and add the following lines.# Here is the list of hosts that are allowed to log in via telnet
#
198.68.35.21 ACME accounting location 1 machine
#Lets not allow location 3 until the office reopens.
#198.68.35.26 ACME accounting location 3 machine
#
Restrict users to a specific application
The system administrator may optionally limit a user to run a specific application. This is accomplished using the c_start..bat file logon scripting technique. A detailed example and description is on page
*.The Georgia SoftWorks Windows NT Telnet Server has recently pioneered and introduced another expected but missing feature in the NT Telnet world. Typically when a user password is expired connections are simply refused by NT telnet servers. This is not the case with the Georgia SoftWorks Windows NT Telnet Server. The user is prompted for the new password just as if they were logged on locally to the NT Server.
Integrated with Windows NT Security
The Georgia SoftWorks Windows NT Telnet Server in integrated with Windows NT security, adhering to the native security already existing on Windows NT.
The Georgia SoftWorks Windows NT Telnet Server is the fastest Windows NT Telnet Server available. The Georgia SoftWorks NT Telnet Server was designed to work in the most demanding industrial and commercial applications. This means that is must have reliable and consistent operation all of the time. It does not matter if there is one connection or 100 connections. It is dependable, reliable, consistent and robust.
Speed Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Fast, Fast, Fast! |
|
Yes |
Yes |
Compression for slow speeds |
N/A |
Yes |
No |
Slow Link, Internet Support |
N/A |
Yes |
Yes |
Proprietary performance algorithms |
N/A |
Yes |
Yes |
Proprietary code optimizations |
N/A |
Yes |
Yes |
|
|
|
|
The Georgia SoftWorks Windows NT Telnet Server provides incredibly fast screen updates. In fact the fastest on the market. Several optimizations have been implemented with respect to screen updates. Fox example when data is sent from the server to the client only the screen data that has changed is sent.
Keyboard response is also incredibly fast. When you type a character it is displayed immediately. A fast typist will have to work hard to outrun the keyboard response of the Georgia SoftWorks Windows NT Telnet Server.
Compression for slow link speeds
The Georgia SoftWorks Windows NT Telnet Server compresses data to increase the overall throughput of data. Incredible performance optimizations are utilized when using the Georgia SoftWorks Telnet Client
Slow link and Internet optimizations
Many access the host system via slow dialup links or by the Internet. Significant performance optimizations are realized when using any telnet client.
Proprietary performance algorithms and code optimizations.
To accomplish the desired performance, the NT Telnet Server designers used object oriented C++ for the foundation of the software, providing a modular and easily extensible and maintainable design. In addition to sophisticated performance algorithms, all time critical sections of the software are written in highly optimized C code.
Failure Detection/Recovery Pack
For Industrial applications excellent failure detection and recovery is expected and required. This is one area that separates the toys from the tools. Georgia SoftWorks pioneered every feature listed on this page. Some have been copied but none have been equaled. The ability to operate in industrial and commercial environments was a design goal from the beginning not an afterthought. Commercial application require that remote link, PC and Client failures be detected and handled as to not impact the other users of the system.
Failure/Recovery Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Complete Session Cleanup |
Yes |
Yes |
Yes |
Complete NTVDM Cleanup |
Yes |
Yes |
Yes |
Server Side Inactivity Timer |
Yes |
Yes |
Yes |
Server Side Heartbeat |
Yes |
Yes |
Yes |
Client Side Heartbeat |
Yes |
Yes |
No |
Graceful Termination of DOS Applications |
Yes |
Yes |
Yes |
Termination Scripts |
Yes |
Yes |
Yes |
Table 3 - Failure/Recovery Pack
The Georgia SoftWorks Telnet Server for NT provides features that ensure that all telnet sessions are properly terminated, even during abnormal client and link failures. Many internal session cleanup methods are automatic; others are configurable using the different Inactivity and Heartbeat timers, termination strings and scripts. Properly terminating telnet sessions ensure that all sessions are available for use and that problems do not accumulate over a long term.
The Georgia SoftWorks Telnet Server has employed very complex and sophisticated proprietary algorithms to detect, identify and eliminate "orphanded" NTVDM’s directly initiated by applications when using telnet. In many cases orphaned NTVDM’s or processes can consume all of the server’s processing power rendering the server crippled or useless. Realizing that NTVDM cleanup is essential in industrial, commercial and mission critical applications, a great amount of design and development resources were expended to ensure proper operation in this area.
Server Side Inactivity Timer allows implementing an optional administrative policy to terminate sessions after a period of inactivity.
For example; ACME Company purchased Georgia SoftWorks Telnet Server with a single session. User Bob connects a session locks his office and goes home. No one else can connect due to the licensing limit.
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 3rd 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.
The Server Side Heartbeat Timer is used for setting the frequency in seconds which to poll the 3rd 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.
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.
Example - Set the Georgia SoftWorks telnet client side heartbeat
gs_clnt.exe /H1800
specifies a heartbeat time of 30 minutes (1800 seconds = 30 minutes). Normally there is no need to change this value.
To change the Client Heartbeat
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 termination string is a comma delimited list of keystrokes that you want to send to the shell ( or your application) before it is terminated due to either the Client Heartbeat timeout or the Server Side Inactivity timeout. No extra white space is allowed. The string is not case sensitive. For example you must specify '
shift-c' to produce a capital 'C'.The following control key designators are defined.
The following special characters are defined.
Also a special operator is defined.
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. By default a 1-second pause is injected between keystrokes, however some specific cases may require the use of the
Sleepxx operator to introduce additional delay.
To ensure graceful termination you may want to enter the string "e,x,i,t,ENTER" to exit the shell. Once the specified application is terminated by the user-specified string, the above string will complete the graceful termination process. This string sends the command exit and then enter which are the commands to terminate a session. You must be sure that the user defined termination string does indeed terminate the application before sending the "e,x,i,t,ENTER" string otherwise unintended characters will be sent to the application.
Example - Graceful termination: Amortization program - link failure.
We will continue to use the amortization program from the previous example. 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
Termination scripting is analogous to the Logon Scripting except it is executed when the telnet session is terminated. The commands within the file
cleanup.bat are invoked upon termination of a telnet session. This is invoked with both normal and abnormal terminations. Cleanup scripting is available on both a global and per user basis as with Logon Scripting.NOTE: No applications that require user input are allowed in the cleanup scripts.
It is especially useful for properly upmapping network connections such as drives. If you do not unmap drives when terminating the session you may be unable to connect to them the next you logon. The cleanup.bat file allows automatic unmapping of drives upon termination of the telnet session.
Example - Termination Script: Cleanup.bat file unmapping the "f" network drive
The system administrator has set up user "Adam"s logon script to map drive "f" as a network drive. In user "Adams" cleanup.bat script the system administrator will un-map the drive when the session is terminated.
Step 1. Create directory
c:\gs_tnet\scripts\Adam
Step 2. Create batch file cleanup.bat
Step 3. Add the following line.
net use f: /d
Step 4. Save file and exit.
This will unmap the f drive after the session is terminated.
NOTE: Please see the section on logon scripting to determine the location for the cleanup script files. (Page
*)
The Georgia SoftWorks Windows NT Telnet Server provides full support for DOS Legacy applications. When you run DOS legacy applications using our NT Telnet Server it is as if you are running them locally. We support DOS Character Mode Color graphics including the line and box characters.
With our client you can use the MOUSE just as you do locally. This was another feature pioneered by Georgia SoftWorks. The function keys and special characters also works and display as expected.
Legacy Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Mouse |
Yes |
Yes |
No |
DOS Character Mode Color Graphics |
N/A |
Yes |
Yes* |
Function Keys |
Yes |
Yes |
Yes* |
Special Characters |
Yes |
Yes |
Yes* |
Screen Sizes other than 25 x 80 |
Yes |
Yes |
Yes* |
Alt key support for all emulations |
Yes |
Yes |
Yes |
|
|
|
|
* As supported by the Terminal emulation mode
When using the Georgia SoftWorks Telnet Client the Mouse works as if you are sitting locally at the server.
DOS Character Mode Color Graphics
DOS Character Mode Color Graphics is fully supported. This includes the full range of DOS Character mode Colors. All of the 256 possible background/foreground color combinations are supported.
The function keys works as expected. With the Georgia SoftWorks Windows NT Telnet Server the function keys operates as if you are sitting at the server and running the application locally. For 3rd Party clients the function keys are supported as per the emulation specified. Please note that some function keys are not supported by various emulations.
All characters with character codes between 0x00 through 0xFF are supported and displayed properly when using the Georgia SoftWorks Telnet Client and conforming third party client emulation’s.
Screen Sizes other than 25 x 80
You may place the Mode command (as described on page
*) in a logon script to set screen sizes. Please note that most UNIX Telnet clients default to 24 rows while NT and DOS applications default to 25 rows. Thus you may have to adjust your UNIX telnet client row count settings to see all the rows of yourNT or DOS application. Alternative you may need issue the modes con: lines=24 command. Note: if you issue this command you will not see the last row of your application.
Alt Key Support for all emulations
Alt keys are completely supported. For 3rd party client Alt key operations see page
*.When using 3rd party clients, comprehensive terminal emulations are a must. Not just offering a wide range of terminal emulations but they are also correctly implemented!
Emulation Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
SCO Console |
N/A |
N/A |
Yes* |
DEC VT100/220/320/420 |
N/A |
N/A |
Yes* |
Wyse 50, Wyse 60 |
N/A |
N/A |
Yes* |
AT386 |
N/A |
N/A |
Yes* |
IBM 3101, IBM 3151 |
N/A |
N/A |
Yes* |
Perfect PC |
N/A |
Yes |
No |
|
|
|
|
* As supported by the terminal emulation mode
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 page
*).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
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 3rd 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:
gwtn_term
For example to select SCO Console emulation you would enter:
set gwtn_term=2
in the Logon Script for a particular user.
NOTE: No spaces are allowed when setting environment variables.
For example:
set gwtn_term=2 is correct
set gwtn_term = 2 is not correct
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 3rd 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 3rd party client. The graphics mode prompt indicates the recommended selection when SCO Console emulation is selected.
Replace PC graphics characters with star characters:
This simply replaces PC graphics characters with the "asterisk" character,
Translate PC Graphics characters:
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.
SCO Console special handling (recommended)
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 3rd 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:
gwtn_graphics
For example to select star graphics character substitution you would enter:
set gwtn_graphics=0
in the Logon Script for a particular user.
NOTE: No spaces are allowed when setting environment variables. For example:
set gwtn_graphics=2 is correct
set gwtn_graphics = 2 is not correct
Color or Monochrome Presentations
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 3rd 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:
gwtn_color
For example to select a color presentation you would enter:
set gwtn_color=1
in the Logon Script for a particular user.
And to select a monochrome presentation you would enter:
set gwtn_color=0
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.
Many applications take advantage of the "Alt" key. However many keyboards and terminal emulations do not support the "Alt" key. The Georgia SoftWorks Windows NT Telnet Server allows the "Alt" key sequence to be transmitted to an application by providing a substitute key sequence (the Alt Prefix) for the "Alt" key. The default Alt Prefix is "Ctrl-b".
For example, in order to transmit "Alt-f" you will type:
Ctrl-
b and then f.(Depress Ctrl then b, release the keys and then depress f).
In order to really type in the AltPrefix character from the keyboard you will have to type it twice, like Ctrl-b Ctrl-b to get the Ctrl-b.
A different Alt Prefix can be configured using "AltPrefix" parameter in the registry editor. The default value is set to two 0x02 which is the ASCII value of Ctrl-b, Other values are as follows:
AltPrefix Value |
Key Sequence entered by User |
0x01 |
Ctrl-a |
0x02 |
Ctrl-b |
0x04 |
Ctrl-d |
0x06 |
Ctrl-f |
0x0e |
Ctrl-n |
0x0f |
Ctrl-o |
0x10 |
Ctrl-p |
0x12 |
Ctrl-r |
0x14 |
Ctrl-t |
0x15 |
Ctrl-u |
0x16 |
Ctrl-v |
0x17 |
Ctrl-w |
0x19 |
Ctrl-y |
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
As you would expect the most powerful and useful features are standard with the Georgia SoftWorks Windows NT Telnet Server. Everything from True Client Side Printing, Logon scripting, Session monitoring to Programmatic access to the server. These are not marketing or sales features but useful and powerful features requested and used by telnet users around the world.
Power Features Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Session Monitoring |
Yes |
Yes |
Yes |
Logon Scripting |
Yes |
Yes |
Yes |
Programmatic Access to server |
Yes |
Yes |
Yes |
True Client Side Printing |
Yes |
Yes |
Yes |
- Enhanced Method |
Yes |
Yes |
No |
- Open Method |
Yes |
Yes |
Yes |
- Default Method |
Yes |
Yes |
Yes |
High Performance client Included that can be installed at as many locations as you choose at not extra cost! |
Yes |
Yes |
Yes |
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 local 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.
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.
You may exit the Session Monitor either by the File then Exit Menu item or depressing the <ESC> key
There are many uses for session monitoring a few are listed.
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
"InstallationPath\scripts\UserLoginID\k_start.bat" or
"InstallationPath\scripts\UserLoginID\c_start.bat"
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.
The system administrator must ensure that the directory permissions for the above files and directories are correct. Remember the user and the SYSTEM must be able to read the batch file. They are executed in the security context of the user.
Example - Logon Scripting: Automatic Execution of a program upon connection
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
c:\gs_tnet\scripts\nurse
Step 2. Create batch file k_start.bat
Step 3. Add line to k_start.bat
c:\medical\medical.exe
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.
Example - Logon Scripting: User restricted to execute only a specific program.
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
c:\gs_tnet\scripts\bill
Step 2. Create batch file c_start.bat
Step 3. Add line to c_start.bat
d:\amor\amortize.exe
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.
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.
Example - Global Logon Scripting: Automatic Execution of a program upon connection by ALL users
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
c:\medical\medical.exe
Step 3. Save file and exit.
Now when 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.
Programmatic Access to the Telnet Server
Note: Programming skills may be required to understand the following section.
Developers may take advantage of the programmatic interface to the Georgia SoftWorks Windows NT Telnet Server. Programmatic, language independent access to the Telnet Server allows developers to write an application that (when run under the Telnet Server environment) takes control of its input and/or output from/to the client. This can be utilized to create a custom or highly specialized communications application. The Telnet Server still maintains critical functionality such as logon, security, application launch and termination. Normally the application before it terminates will release control to the telnet server.
The Telnet Server communicates with the client through a WINSOCK socket. A protocol/mechanism is provided that allows a custom application to take and release control of the socket. Objects involved in taking and releasing control of the socket are passed through environment variables as are described below.
Note1: All of the above mentioned events are autoreset events.
Note2: The above environment variables are automatically injected into the session's environment and will vary from session to session. Please do not attempt to modify those variables or set them in the autoexec files or Control Panel/System/Environment.
Please see the file interface.c included on the installation disks for a code sample. interface.c contains a short program that takes control of the input and output and echoes characters to the client until a lowercase q is encountered.
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.
Multiple (up to 3) printers may be used on a per user basis. Georgia SoftWorks offers several printing methods for the telnet user that will address most printing requirements. They are
The Default Printing method uses standard server printing facilities. When a telnet user prints, the printer output destination is exactly the same as if the user is sitting at the server and initiated the print. The destination may be local to the server or any remote printer that has been captured by the
net use command. No setup is required for Default printing.Enhanced printing is an advanced feature of the Georgia SoftWorks NT Telnet Client that allows printers accessible to the user’s client computer to be used when printing with telnet. The Client computers default printer is used of no telnet client command line parameters are specified. The telnet user can override the default printer using command line arguments when initiating the client. Also multiple printers can be utilized by configuring additional client side printers as described below.
The Open printing method allows the telnet user to specify the printing command that telnet will use when processing print jobs. For example if the user wants to send output to a shared printer then the "print /d" command can be configured. Another example is sending output to a printer with an IP address that is on the network but is not shared or visible to the server. In this case the telnet user would specify the "lpr" printing command. Other valid print commands can be configured as the user’s requirements dictate. Please be knowledgeable with the printing commands you select.
Setting up True Client Side Printing
There are up to three steps in setting up True Client Side Printing.
A Virtual Printer(s) is defined that redirects the output from your application. The Georgia SoftWorks Telnet Server queries the Virtual Printer queue for new print jobs. When a print job enters 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 the proper 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. Up to three (3) Virtual Printers may be defined on the server. (This will allow up to three (3) printers to be used for each client.). A Printer Index is used to identify and correlate the various printer setups. The printer indexes are 1, 2 and 3. For the Virtual Printer Setup the Printer Name and Share Name require printer indexes. The following setup is for a single printer (Printer Index 1).
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.
If you need to support more than one client side printer per user at a time then repeat steps 1 through 11 using the other two Printer Indexes. This involves replacing the printer name in step 8 with either GwtnPrinter2 or GwtnPrinter3 and the share name in step 9 with either GwtnPrinterShare2 or GwtnPrinterShare3.
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:
net use lptx: \\servercomputername\GwtnPrinterSharey
Where
The next is an environment variable that indicates the True Client Side Printing method chosen. The environment variable is:
GWTN_LOCAL_PRINT_METHOD
and valid values are:
The syntax is:
set GWTN_LOCAL_PRINT_METHOD=Open
orset GWTN_LOCAL_PRINT_METHOD=Enhanced
If the environment variable does not exist then the True Client printing method is the
Default printing method. This prints as if the user is sitting local at the server. There is no setup required for the Default printing method.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 any printers accessible to the client system (for example the default printer) 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 Enhanced Print Method is very useful to users that connect across the Internet or via RAS. Enhanced printing may also be used in many other scenarios. The Enhanced True Client Side Printing Method is a feature of the Georgia SoftWorks Windows NT Telnet Client and is not available with 3rd party clients. Print output is sent to the client’s computer default or local printer(s). Client parameters also exist that allow printers other than the default printer to be used with Enhanced printing.
The first example describes the basic Enhanced Printing setup and the second example describes using multiple client side printers and the third describes the override feature.
Example - Enhanced Printing: Printing to my local printer when connected across the Internet or RAS
I have sales people 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 application software that they use prints to lpt3. How do they have printer output sent to their laptop portable printers?
This is an excellent opportunity for the Georgia SoftWorks Enhanced True Client Printing Method.
Remote Locations |
Connection |
Corporate Server |
|
|
|
|
Server Name : SolomanThe virtual printer has been set up with: Printer Name: GwtnPrinter1 PrinterShare: GwtnPrinterShare1 |
|
Telnet Client :: Georgia SofWorks Telnet Client for Windows NTClient Operating System: Windows 95/98/NT The attached printer is the default printer for each laptop. The Printer driver is set to Generic/Text. |
Logon Script :sDirectory: C:\gs_tnet\Scripts\SuperSalesMan and Directory: C:\gs_tnet\Scripts\SuperSalesWoman Filename: k_start.bat net use lpt3: \\soloman\GwtnPrinterShare1 set GWTN_LOCAL_PRINT_METHOD=Enhanced |
Figure 5 – True Client Side Printing: Printing across the Internet or RAS
Note:
The Logon Scripts can be implemented in a variety of ways depending on the requirements. For example a global logon script could be created for all telnet users. In the example above we used user specific scripts for each salesperson that might use telnet.Important Information
User Name(s): SuperSalesMan and SuperSalesWoman
Server Computer Name: soloman
Telnet Client: Georgia SoftWorks Windows NT Telnet Client
Client Operating System: Windows 95/98 or Windows NT
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 each user needs to have the following commands:
Edit the users logon script k_start.bat and add the following commands:
net use lpt3: \\soloman\GwtnPrinterShare1
set GWTN_LOCAL_PRINT_METHOD=Enhanced
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. It is recommended that the printer driver for the default printer be set to Generic/Text.
When the salesman prints to lpt3 the output will appear on the default printer connected to the salesman's client computer. This same methodology is used for either a single or multiple sales people. If the client needs to support more that one printer at a time please read the section on Multiple Client Side Printers - Carefully.
Example - Enhanced Printing: Multiple Client SIDE Printers
Setting: remote Physicians office. They have a dot matrix printer that is used for insurance forms and a laser printer for formal letters. The medical software application exists at the main office on an NT server and they are using telnet to access the application. Here an office manager in a physician’s office needs to be able to access two different printers from his client machine. The Medical application is using LPT1 to print the forms and LPT2 for the formal letters.
The main office configured the server machine to have two virtual printers. One is named GwtnPrinter1 and the other is named GwtnPrinter2(As required by the virtual printer specifications. See page
*).
Remote Clinic Locations |
|
Physicians Main office |
|
|
|
Telnet Client : Georgia SofWorks Telnet Client for Windows NTClient Operating System: Windows 95/98/NT The Printer drivers for each printer are set to Generic/Text. Command Line used to invoke the Georgia SoftWorks Telnet Client: gs_clnt.exe /r1=InsurancePrinter /r2=FormalPrinter /H300 |
Server Name : MedicalThe First virtual printer has been set up with: Printer Name: GwtnPrinter1 PrinterShare: GwtnPrinterShare1 The Second virtual printer has been set up with: Printer Name: GwtnPrinter2 PrinterShare: GwtnPrinterShare2 |
|
Logon Script :Directory: C:\gs_tnet\Scripts Filename: k_start.bat net use lpt1: \\Medical\GwtnPrinterShare1 net use lpt2: \\Medical\GwtnPrinterShare2 set GWTN_LOCAL_PRINT_METHOD=Enhanced |
Figure 6 – True Client Side Printing: Using Multiple Client Side Printers per User
Note the correlation between client side command line parameters "/rx" and the Printer Share and Printer names on the server.
Important Information
Server Computer Name: Medical
Telnet Client: Georgia SoftWorks Windows NT Telnet Client
Client Operating System: Windows 95/98 or Windows NT
Dot Matrix Printer Name: InsurancePrinter
Laser Printer Name: FormalPrinter
Virtual Printer to Use: 1 and 2
One the server in the users logon script add the following commands:
net use lpt1: \\MedServer\GwtnPrinterShare1
net use lpt2: \\MedServer\GwtnPrinterShare2
set GWTN_LOCAL_PRINT_METHOD=Enhanced
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 /r1=InsurancePrinter /r2=FormalPrinter /H300
Example - Enhanced Printing: Overide
This is a variation of the previous examples. 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:
/rx=printername or
/rx=\\computername\printersharename
Where
x is (1,2,or 3) the Printer Index number.
|
|
|
|
Server Name : SolomanThe virtual printer has been set up with: Printer Name: GwtnPrinter1 PrinterShare: GwtnPrinterShare1 |
|
Telnet Client :: Georgia SofWorks Telnet Client for Windows NTClient Operating System: Windows 95/98/NT The attached printer is not the default printer for the laptop. The Printer driver is set to Generic/Text. Command Line used to invoke the Georgia SoftWorks Telnet Client: gs_clnt.exe /r1=CustomerColorPrinter /H300 |
|
Logon Script :sDirectory: C:\gs_tnet\Scripts\SuperSalesMan Filename: k_start.bat net use lpt3: \\soloman\GwtnPrinterShare1 set GWTN_LOCAL_PRINT_METHOD=Enhanced |
Figure 7 – True Client Side Printing: Enhanced Printing Override
Important Information
User Name: SuperSalesMan
Server Computer Name: soloman
Telnet Client: Georgia SoftWorks Windows NT Telnet Client
Client Operating System: Windows 95/98 or Windows NT
Color Printer Name: CustomerColorPrinter
Virtual Printer to Use: 1
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:
net use lpt3: \\soloman\GwtnPrinterShare1
set GWTN_LOCAL_PRINT_METHOD=Enhanced
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 /r1=CustomerColorPrinter /H300
When the salesman prints to lpt3 for user SuperSalesMan the output will appear on the color printer.
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 variables are:
GWTN_LOCAL_PRINT_CMD1
GWTN_LOCAL_PRINT_CMD2
GWTN_LOCAL_PRINT_CMD3
They correspond to the handling of print jobs sent to GwtnPrinter1, GwtnPrinter2 and GwtnPrinter3.
And the syntax of the command is:
set GWTN_LOCAL_PRINT_CMDx=PrintCommand %s
Where
The print method and capture is determined by setting the environment variable GWTN_LOCAL_PRINT_CMDx. The most commons commands are the "
print /d:" or the "lpr" printing commands. Other printing commands may be used, as the user’s needs dictate. If the client printer is a shared printer (that is visible from the server) then you should use the "print /d:" command. The lpr command should be used when the host provides a lpd service. The user should be knowledgeable of the print command selected. The syntax of the "print /d:" command could be:set GWTN_LOCAL_PRINT_CMDx=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
The syntax of the
lpr print command could be:set GWTN_LOCAL_PRINT_CMDx=lpr -S Server -P printer %s
where
Other arguments are available for the
lpr command. Please see the help for the lpd service that you are using.Example - Open Printing: Print to a client computer’s shared printer
In my office I have a computer and a printer connected. I also am using a 3rd party telnet client. My system is on the network and my shared printer is visible to the server. 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?
Important Information
User Name: Smarts
Client Computer Name: SmartsComputer
PrinterShareName: SmartsPrinter
Server Computer Name: soloman
Telnet Client: Any - No Restriction
Operating System: Any - No Restriction
The only requirement is that the printer be visible to the server. In other words the printer at the client computer must be shared. Of course the Virtual printer must be defined as described in the Virtual Printer section. The logon script for user Smarts should have the following commands:
Edit the users logon script k_start.bat. and add the following commands:
net use lpt1: \\soloman\GwtnPrinterShare1
set GWTN_LOCAL_PRINT_METHOD=Open
set GWTN_LOCAL_PRINT_CMD1=print /d:\\SmartsComputer\SmartsPrinter %s
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.When the accounting application prints to lpt1 the output will appear on the printer in Ms. Smart's office. This same methodology can be used for as many users as you wish.
Example - Open Printing: Print to a Network Printer
In our building we have a two workgroups. Each workgroup has their own network printer in a common area. Both workgroups have 25 users that telnet to the main server from UNIX workstations and run a database application. We print reports on lpt2. How can we get the reports to be printed on the correct network printer for each workgroup? This is an excellent case for the Open True Client Side Printing method using the lpr command.
Remote Work Group |
|
Company Server |
![]() |
|
|
|
||
|
Server Name : SolomanThe Virtual printer has been set up with: Printer Name: GwtnPrinter2 PrinterShare: GwtnPrinterShare2 |
|
Logon Script for First WorkGroup :Directory: C:\gs_tnet\Scripts\UserName (For each user in workgroup1) Filename: k_start.bat net use lpt2: \\soloman\GwtnPrinterShare2Set GWTN_LOCAL_PRINT_METHOD=Open set GWTN_LOCAL_PRINTCMD2=lpr –S 192.32.200.200 –P WkgGrpPtr1 %s |
||
Telnet Client – Any, No Restriction. Operating System – Any – No Restriction |
Logon Script for Second WorkGroup :Directory: C:\gs_tnet\Scripts\UserName (For each user in workgroup2) Filename: k_start.bat net use lpt2: \\soloman\GwtnPrinterShare2Set GWTN_LOCAL_PRINT_METHOD=Open set GWTN_LOCAL_PRINTCMD2=lpr –S 192.32.200.201 –P WkgGrpPtr2 %s |
Figure 8 – True Client Side Printing: Open Print Method
Important Information
IP Address of the first Host providing the lpd service: 192.32.200.200
Printer Name: WrkGrpPtr1
IP Address of the second Host providing the lpd service: 192.32.200.201
Printer Name: WrkGrpPtr2
Server Computer Name: soloman
Telnet Client: Any - No Restriction
Operating System: Any - No Restriction
The only requirement is that a lpd service exists for the printer to be used. In this case the network printer provides the service. Of course the Virtual printer must be defined as described in the Virtual Printer section. The logon script k-start.bat for users in workgroup 1 need to have the following commands:
net use lpt2:
\\soloman\GwtnPrinterShare2Set GWTN_LOCAL_PRINT_METHOD=Open
set GWTN_LOCAL_PRINT_CMD2=lpr -S 192.32.200.200 -P WkgGrpPtr1 %s
The logon script k-start.bat for users in workgroup 2 need to have the following commands:
net use lpt2:
\\soloman\GwtnPrinterShare2Set GWTN_LOCAL_PRINT_METHOD=Open
set GWTN_LOCAL_PRINT_CMD2=lpr -S 192.32.200.201 -P WkgGrpPtr2 %s
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.When the database application prints to lpt2 the output will appear on the correct network printer for each workgroup. The logon script for each user in the Work Group will need to be modified to contain the same commands. This same methodology can be used for as many users as you wish.
The Georgia SoftWorks Windows NT Telnet Server allows connection with any RFC 854 compliant 3rd party client. This includes generic UNIX, MAC, Windows CE, NT, Wireless clients and more! Most telnet clients are RFC 854 compliant. Many Network Terminal and terminal servers are as well.
Compatibility Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
RFC 854 Compliant |
N/A |
No |
Yes |
Connect from 3rd Party Clients |
Yes |
N/A |
Yes |
Connect from Unix |
Yes |
N/A |
Yes |
Connect from Windows 3.1 |
Yes |
N/A |
Yes |
Connect form Windows 95/98 |
Yes |
Yes |
Yes |
Connect from Windows NT |
Yes |
Yes |
Yes |
Connect from Windows CE |
Yes |
Yes |
Yes |
Connect from Macs |
N/A |
N/A |
Yes |
Connect from Wireless, Handhelds |
|
No |
Yes |
Connect from others RFC 854 compliant platforms |
Yes |
N/A |
Yes |
Connect from Terminal Servers |
|
N/A |
Yes |
RF Wireless handhelds and the Georgia SoftWorks NT Telnet Server:
The Georgia SoftWorks Telnet Server for Windows NT works well with many RF Wireless systems, in particular hand held units. By using Telnet the RF Wireless Hand Held application developer is able to create more generalized applications that will easily work with a variety of manufactures hardware. In addition to development and maintenance cost savings for application developers this added flexibility allows heterogeneous systems to exist allowing customers to utilize existing hardware.
Georgia SoftWorks is committed to providing the best telnet solution for the RF Wireless market. Some tailored features include:
Utility Pack |
Configurable |
Georgia SoftWorks Client |
3rd Party Client |
Change Password |
Yes |
Yes |
Yes |
Remote Reboot of Server |
Yes |
Yes |
Yes |
Special Bell Processing |
Yes |
Yes |
Yes |
The Georgia SoftWorks Windows NT Telnet server provides utilities for the users’ convenience. The utilities reside in the installation directory. The utility names are not case sensitive. Arguments such as NT passwords are case sensitive.
Change Password command line utility
Many times a user wishes to change their password. A convenient method is to use the Georgia SoftWorks Change Password command line utility.
Command: GS_ChPwd
Description: Command line utility that changes a users password
Syntax: Gs_ChPwd <user> <\\computer | domain> <newpassword> <oldpassword>
Arguments: There are 4 required arguments.
Example - Utilities: Change Password
The user "smith" want to change his password on the computer "soloman" from "fast" to "superfast".
Gs_ChPwd smith \\soloman supertfast fast
Reboot NT computer command line utility.
The System Administrator may need to reboot a Windows NT system remotely. The Georgia SoftWorks Windows NT Telnet Server provides a command line utility that reboots a Windows NT computer.
Command: GS_Rbt
Description:
Reboot a Windows NT computer. The computer will reboot about 40 seconds after the command is executed. GUI users will receive a notification.
Syntax: Gs_Rbt [Computer]
Arguments: There is 1 optional argument
[computer name] - the name of the computer to reboot.. If the computer name is omitted then the Windows NT computer that the command is executed will reboot.
Notes: Administrative privileges are required to run this command.
Warnings: The system administrator must be sure that they want to reboot, as all user sessions will be disconnected.
Example - Utilities: Reboot NT System
Reboot the computer soloman
Gs_Rbt soloman
You will then be prompted with:
You have requested to shutdown soloman.
If you continue all applications with unsaved data will be forcibly closed in 40 seconds.
Do you really want to continue? [Yes/No]
You must type either
Yes or No and press <enter>. "Y" or "N" is not valid.In approximately 40 seconds the Windows NT Computer will reboot.
The Georgia SoftWorks Windows NT Telnet Server can intercept a special character outbound to the client and replace it with a bell character.
The Special Character and the location are defined using Registry Values.
Usually the application can identify a normally unused position on the screen that can be used for the placement of the special character when desiring that the bell character be sent.
This location is specified in the registry as described below.
Registry Parameters are located:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters
BellX -
column of the bell character, initialized to 0xffffffff, which makes it inactive.BellY -
row of the bell character, initialized to 0xffffffff, which makes it inactive.BellChar - value of the bell character, initialized to 0x87
All three parameters work for all types of clients, including the
gs_admin. In order to disable the feature: set BellX or BellY to 0xffffffff.
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:
gwtn_tty
And is set to /dev/ttypxxx, where xxx
represents the socket number (handle) for user's session.
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.
In some instances the System administrator may want to eliminate the prompting for a domain when the user is connecting to the telnet server. This can be accomplished by setting the default domain registry variable. This works for 3rd party clients only. Use the command line parameters to set the default domain for the Georgia SoftWorks Telnet Client. (see page
*)This is accomplished as follows.
The key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters\Domain
The new Domain will take effect for all new sessions.
This registry value is initialized to "UNKNOWN" which disables a default domain. The empty string means the default domain. This is equivalent to pressing enter when prompted. This will eliminate prompting for users of all clients.
Can I use a port other than port 23 for the Telnet Server
Yes, you can use an alternative port for the Georgia SoftWorks Windows NT Telnet Server.
You will need to create an entry like:
gstnet 55555/tcp
in the Services file on the server and restart the NT Telnet Server. Replace the 55555 with another port number if necessary. You will have to explicitly specify the alternate port number when starting the connection from 3rd party clients and the Georgia SoftWorks Telnet Client (page
*).On Windows NT 4.0 the services file is located in the directory:
C:\Winnt40\system32\drivers\etc
The file is named Services.
Can I telnet to the Telnet server and then telnet to another server?
The short answer is Yes. If you telnet to the Georgia SoftWorks Windows NT Telnet server and you then want to telnet to another Georgia SoftWorks Windows NT Telnet server you simply run the gs_clnt.exe program at the DOS command line. However if you want to telnet to a non-Georgia SoftWorks Windows NT Telnet server you will need a 3rd party DOS client that can be executed from the command line.
I can't logon from Telnet, what should I do?
The typical rule is that if you can log in locally to the NT machine then you can logon from telnet. Make sure that you can logon locally. Users must have "log on Locally" access permissions. From "User Manager" or "User Manager for Domains" choose the menu item "Policies" which is a drop down. From the drop down choose "User Rights". A "User Rights Policy "dialog appears allowing you to add the "Log on Locally" Right for the group.
However if the local group Gwtn Users exists you must be a member of this group to logon via telnet.
I am the Administrator but gs_admin.exe says I do not have administrative privileges?
To participate in Session Monitoring a user must belong to the local 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.
You need to use the COLOR Command in a logon script. Here is the syntax.:
COLOR [attr]
Sets the default console foreground and background colors.
attr
Specifies color attribute of console outputColor attributes are specified by TWO hex digits -- the first corresponds to the background; the second the foreground. Each digit can be any of the following values:
0 = Black 8 = Gray
1 = Blue 9 = Light Blue
2 = Green A = Light Green
3 = Aqua B = Light Aqua
4 = Red C = Light Red
5 = Purple D = Light Purple
6 = Yellow E = Light Yellow
7 = White F = Bright White
If no argument is given, this command restores the color to what it was when CMD.EXE started. This value either comes from the current console window, the /T command line switch or from the DefaultColor registry value.
The COLOR command sets ERRORLEVEL to 1 if an attempt is made to execute the COLOR command with a foreground and background color that are the same.
Example: "COLOR fc" produces light red on bright white
I want to change the size of the window. The client is set to 80x40 but when it connects to the server it reverts back to 80x25.
The mode command will address this issue.
Mode con[:] [cols=c] [lines=n]
Try putting
mode con: LINES=40
in your logon script.
How do I eliminate prompting for the various settings when using 3rd party clients?
The answer is yes. Environment and registry variables exist that when defined will be used as defaults eliminating the prompting for those values when connections are established. The environment variables can be set in either Global or Per User Logon Scripts. For a list of the environment variable please see the section on 3rd party clients (page
*) in the User Manual and/or the section on Environment (page *) and Registry variables (page *).Can I eliminate prompting for the Host, UserID and Password?
When using the Georgia SoftWorks Telnet Client the Host, User ID and Password can be specified as a command line options. Either invoke the Telnet Client from a command prompt with the options or for more permanent settings modify the short cut. Please see page
* for the section in the User Manual on Georgia SoftWorks Telnet Client Command line options.Can I eliminate prompting for the Domain?
Yes. For all 3rd party clients a registry variable can be set that will contain the default domain for all connections. This is described on page
*. When using the Georgia SoftWorks Telnet client you may use command line options to set the default domain to eliminate prompting. This is described on page *.Can I connect from older systems with DOS or Windows 3.1
Yes however you must have a 16-bit client. The Georgia SoftWorks Telnet Client is 32 bit. And require Windows 95/98 or NT. Several 16-bit clients can be found on the Internet.
Can I have the user deposited into a specific directory upon connection?
Yes. You may set the environment variable
gwtn_home_dir in the logon script on either a global or per user basis.set gwtn_home_dir=d:\users\tom
Is there any way to get the bell to sound on the client?
For customers that have control over the development of their own applications the answer is yes. Please see page
* for detailed instructions.Can I start and stop services when connected via telnet?
Yes. The commands "
net start" and "net stop" provide this ability. Please execute the "net ?" from an NT command prompt for the details on the "net" commands and parameters.Can I configure user information when connected via telnet?
Yes. The commands "
net user","netaccount", etc. provide this capability. Please execute the "net ?" from an NT command prompt for the details on the "net" commands and parameters.
Discussion: Orphaned NTVDM's and Windows NT Telnet Servers
What are NTVDM's and why are they important for Windows NT Telnet
?NTVDM's are NT Virtual DOS Machines. For Windows NT to run DOS programs, NT creates a NT VDM that provides a DOS environment for the DOS program to reside.
When are NTVDM's created?
When DOS applications are executed a NTVDM is created. A normal Telnet scenario is to connect to a Windows NT system and run a DOS application. NT will create a NTVDM. This is all fine and normal.
What are Orphaned NTVDM's?
Normally during a Telnet session running a DOS application, upon completion of the application the user will exit the application properly. In this situation the NTVDM is properly terminated.
However problems occur when a Telnet session running a DOS application abnormally terminates.
The Telnet session will normally terminate however the NTVDM will not terminate. This leaves what is called a orphaned NTVDM. Some term this rouge or phantom NTVDMs or processes.
Why is this a concern?
These orphaned NTVDM's are a serious problem to the NT System. They will start consuming all the processing resources of the Windows NT system that results in the severe degradation of all other processes on the system. This is not just a slight slowing down of the system but a slowing down to the point of the system being useless by most users standards. The most common way to clear the NTVDM is to reboot the NT system. However if you are skilled you can kill the orphaned processes.
What types of events cause orphaned NTVDM when using Telnet?
Any abnormal terminal of a client can cause an orphaned NTVDM. One easy way to create an NTVDM with telnet simply to power off the Client PC while running a DOS program via Telnet. For example:
At this point a NTVDM is created. You can observe this on the Telnet Server by:
Having multiple Telnet sessions connected running DOS applications when an abnormal termination occurs can exacerbate this problem.
Frequent scenarios for abnormal terminations
What can be done about Orphaned NTVDM's?
The Georgia SoftWorks Windows NT Telnet Server automatically provides advanced detection and elimination for orphaned NTVDM's. Unlike others that claim to handle this serious problem, the Georgia SoftWorks Windows NT Telnet Server actually detects and eliminates these process consuming tasks in a remarkably quick time minimizing the impact on other users and tasks on the system. The Georgia SoftWorks Windows NT Telnet Client accomplishes detection via the configurable heartbeat timer and third party telnet clients utilize the configurable Server Side Heartbeat Timer. Upon detection sophisticated algorithms are used to identify orphaned NTVDM and eliminate them.
Discussion: PIFs and your MS-DOS application's Performance
Information derived and extracted from the Microsoft Knowledge base.
Windows NT provides a fully-integrated command prompt that enables you to launch both Windows-based and MS-DOS-based applications. Although the concept of running an MS-DOS-based application in a Windows-based environment may be familiar to you, Windows NT handles this somewhat differently than Windows (16-bit) does.
The essential difference lies in the command prompt itself; under Windows NT, the command prompt is a 32-bit Windows NT-based application, not the virtual MS-DOS machine you would expect from Windows. Under Windows NT, until you start an MS-DOS-based application, no virtual MS-DOS machine is created. Furthermore, once you start an MS-DOS-based application, its virtual MS-DOS machine is used for all subsequent MS-DOS-based applications started from the same command prompt.
As in Windows, each MS-DOS-based application can have a program information file (PIF). If there is no PIF for a particular application, the default PIF, _DEFAULT.PIF, is used. Because Windows NT only uses the PIF from the first application started in any given command prompt, you may need to take special care in the way you start your applications. For example, if you design a PIF that allocates some EMS memory, it is important that you start the associated application first; otherwise, the EMS memory may never be allocated. You may start a Windows NT command prompt and then run the MS-DOS command, MEM, to see how much memory you have free. Because MEM is another MS-DOS-based application, Windows NT creates a virtual MS-DOS machine, probably using _DEFAULT.PIF. After MEM finishes, you start the application you created the PIF for. Unfortunately, because _DEFAULT.PIF doesn't instruct Windows NT to allocate EMS memory, your application reports that it can find no EMS memory. Rechecking the PIF you created does not solve the problem. You need to start another command prompt and then make sure to start your EMS-requiring application first, before you start any other MS-DOS-based applications.
There is one more difference to be aware of: each PIF contains a pointer to AUTOEXEC and CONFIG files. Usually these default to the Windows NT versions, AUTOEXEC.NT and CONFIG.NT. If you want to change environment variables for your MS-DOS-based applications, you need to point their PIFs to different files or modify the default ones. (To see these files and their locations, run PIF Editor and choose Windows NT.)
If you are not satisfied with the performance of your MS-DOS-based applications on Windows NT, try the following:
Windows NT 4.0 keeps the same setting in the property (right click) of the MS-DOS-based applications.
• If the application is in a window and the video display performance is slow, try full-screen mode. Windows NT 4.0 "screen folder" provides this setting.
• Disable the Compatible Timer Hardware feature in the _DEFAULT.PIF or the application's program information file (PIF) under the NT-specific section of PIF Editor. Since this feature causes a decrease
in performance, it should be used only if it is required to make an application to run with Windows NT. Windows NT "program folder" under "Windows NT" section provides this setting.•If the application is in a window and seems to pause periodically, try disabling Idle Detection in the Advance section of that application's PIF. Windows NT "misc folder" provides this setting in a form of a slider bar called "idle sensitivity".
•If the MS-DOS-based application can be configured for printing, choose LPT1, LPT2 over parallel port. Most of the applications use Int17 to print when configured for LPT<x>. If you select parallel port mode, these applications print directly to printer ports. Parallel mode is significantly slower in Windows NT compared to Windows 3.1.
Environment Variables Set by the User
Many environment variables exist for the users convenience. They are available to use in local and global login scripts to set defaults to eliminate prompting as well as setting values for special uses. The details are described it the appropriate section in the user manual however we have included a quick reference list here.
gwtn_color - Sets Color or Monochrome presentation for 3rd party clients (page
*).gwtn_encrypt_session – Activates Data Stream Encryption for the session (Global or Per User) (page
*).gwtn_graphics - Sets the graphics mode for 3rd party clients (page
*).gwtn_home_dir – Selects the home directory that the User will be deposited into upon connection (page
*).gwtn_local_print_cmdx - Indicates the printing command/index used by the Open Print Method (page
*).gwtn_local_print_method - Indicated the True Client Side Printing method chosen (page
*).gwtn_term - Sets terminal emulation for 3rd party clients (page
*).lra_termination - Define the termination string that is sent to an application upon detected failures (page
*).Environment Variables Set by the Telnet Server
Many environment variables are set by the Telnet server and are available to the User or Programmer.
gwtn_agntpid - Process id of the Agent Process handling the user session.
gwtn_clientip - IP address of the client computer
gwtn_hsocket - Socket handle of client session
gwtn_tty - The Georgia SoftWorks NT Telnet Server creates a tty name on a per session basis(page
*).
Many registry variables exist for provisioning the system. Registry variables are an excellent method to configure software as to utilize already leaned skills by the system administrator. There is no need to learn yet another interface to provision the software. He is a list of the registry variables and a brief description of their use. Please see the appropriate section in the User Manual for complete descriptions.
All Registery values used by the Georgia SoftWorks Windows NT Telnet Server are stored in the following Registry path.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ GS_Tnet\Parameters
System Signature - IMPORTANT PLEASE READ
The registration software obtains a system signature that is unique to your system. This signature is an added security measure to inhibit unauthorized personal to obtain working copies of the NT Telnet Server.
The signature is comprised of hardware and software identifiers that exist on your system that make the target system unique. These identifies are hashed into a Product ID and a Serial Number can be generated from this Product id.
If major hardware components of your system are removed, replaced or modified your Serial Number may discontinue to work and you may need a new Serial Number to obtain access to the NT Telnet Server. Please contact Georgia SoftWorks Technical Support if needed.
For Technical Support.
In order to keep Technical Support Free please help us to keep our cost down.
If the question is not an emergency, please use e-mail at support@georgiasoftworks.com. We try to respond within 24 hours.
Or Call 706.265.1018 EST, M-F 9:00 a.m. to 5:00 p.m. and have your Product ID ready