Pragma TelnetServer is executed automatically by the Pragma InetD service, when a user connects to the server using any telnet client.

Users need to type a username, password and domain of a valid Windows account with "Log on Locally" rights to log into TelnetServer. Leaving the domain prompt blank will cause the server to search for the username, beginning with the local accounts, then the current domain, followed by any trusted domains. A delay during user authentication might be caused by this network search. Speed up the process by entering a domain. The domain\username syntax can be used at the login name prompt. If the domain is entered with the username, the user will not be prompted for domain later. If the password needs to be changed, the user will be prompted to change the password, then will be returned to the logon prompt. After login, the user may be prompted for session options that can be configured by the server administrator. Enter the best matching value for each prompt. There is an Auto Logon feature to automatically logon all users with the same user id.

After logon the user is given a command shell session and the security context is set to represent the logged on user account. Most console applications can be used during the telnet session.

To end the telnetsession, exit the program or user shell in a normal fashion. This will close the session in a graceful manner.

Text Editors

Many text editors can be used in a Pragma TelnetServer telnet session. The DOS edit program, vi from the MKS Toolkit, and xvi, a freeware vi editor, can all be used without problem. The vi editor from the Windows Resource Kit can be run using the Wrapper Technology. A version of Emacs can be obtained from the University of Washington's Windows port of Emacs. Version 19.34.2, or later, will work.

User Home Directory and Command Profile\Login Script

If a user's home directory, profile, and login script are specified in the Windows account database, accessed by the Windows User Management, Pragma TelnetServerwill change to that home directory when the user logs on, and execute the profile and login script. A home directory and login script can also be specified in the TelnetServer configuration. See User General Settings for more information on specifying a home directory, and Full Console Settings and Stream Settings Startup Program for more information on setting a login script. If no home directory is specified, the user's user profile directory is used.

The Windows Logon Script can be turned off for telnet sessions under User Logon configuration.

telnet keyboard mapping

If a key appears not to work from the telnet session, check the keyboard mapping of the client application. Many terminal emulators do not map all the keys. They require the keys to be added to the keyboard mapping. Common examples of these are PAGEDOWN and PAGEUP, which many telnet client programs do not map initially. Check the telnet client for documentation on how to add entries into the keyboard mapping table. The keys will need to match the emulation sequences defined in Appendix D.

Instructions for ALT Key keyboard mapping

Windows intercepts keys supplemented with the ALT key from programs (like a telnet client) and interprets them as local menu keys. As a result, some other keys have to be entered at the telnet client in order to have them be mapped to the ALT key by Pragma TelnetServer. By default, CTRL-A has been re-mapped to act as the ALT key in a telnet session. Many applications require the ALT key and most terminals do not specify an ALT key. For example, when working in EDIT.COM, to access the File Menu, instead of pressing ALT-F, press CTRL-A (release), then F to represent ALT-F. When using Pragma's Console TELNET Client this is not needed, all keys act as they would normally. The ALT key can be re-mapped under the User Keyboard configuration.

Instructions for Edit keys

Pragma TelnetServer recognizes all editing keys (INS, DEL, END, etc) and all cursor keys. To use the number pad keys, make sure that NUM-LOCK is disabled. See Appendix D for the expected escape sequences for the supported terminal emulations.

Instructions for viewing graphic characters

PC applications use the PC's character set to generate character graphics. For example, the TREE and EDIT DOS commands use line drawing characters from the PC character set. Many terminal emulator's graphic character set is different than that of the PC, for example Digital VT terminals. In order to get all graphic characters properly displayed via Pragma TelnetServer, use a telnet client that supports character set or font selection. Choose the character set or font that is based on the IBM PC character set.

To change the displayed character from the client sent character, characters can be defined using the charmap.ini file. Following the examples in the file, assign a new value to a received character. This will improve many displays. See User General Settings for more information.

Server Environment Variables

When the server creates the session, it adds or modifies environment variables to identify properties of the session.

Connect 1000+ telnet sessions to a machine running Pragma TelnetServer

In order to connect 1000+ telnet sessions to a machine, the hardware must be up to the task. Below is an example of a machine that will handle 1000+ sessions:

In addition to the above, the "Desktop Count" option needs to be set to 20. The Desktop Count option is located under:   Local Server Configuration-> InetD. Click on the help button on the Local Server Configuration dialog to read more about Desktop Count.

NOTE: The above example is ONLY for connecting 1000+ telnet sessions and getting telnet command shells. When a third-party application is run on the same machine after making a telnet connection, more resources are consumed. Therefore, the above hardware example may NOT be enough to connect 1000+ telnet sessions and then launch many instances of a third-party application.

Microsoft Powershell

Pragma TelnetServer supports Microsoft Powershell. Cmdlets and executables of the Powershell can be run within the telnet sessions launched by Pragma TelnetServer.

Microsoft's Windows PowerShell is a new generation .NET based modern shell which can be considered a replacement of cmd.exe. PowerShell provides full access to .NET commands and APIs and supports C#, VB.Net, VB languages thus making it much more powerful than even UNIX shells. Powershell can be extended through cmdlets and other documented methods.

Pragma TelnetServer provides full support of Microsoft's Windows PowerShell. Powershell can be invoked from the command line by typing "powershell" or configured to be the default shell by changing configuration info using "Pragma Local Server Configuration" graphical program.

Powershell can be run in Pragma's Advance Console or Full Console mode. It cannot be run in Pragma "Stream" mode as it needs richer I/O interaction support..