Release Date: 9/16/02

Fixes:

• FIX: Samr pipe forced closed before session ends 

Release Date: 5/29/01

Enhancements:

• Child processes terminated by the monitor child process option can be logged to the Application Event Log. For each user key under the HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\InterAccess\TelnetD\Users\ key add a string value "LogTerminatedProcs" with a value of "yes". 
• Even more sessions with small SharedSection setting 
• Interaccess Manager now lists up to 512 users 
• PassThru mode available - This is a purely stream session. This should be used for direct communication between client/server for entire session. Set a string registry value "FullPassThru" with a value of "yes" for each user key under the HKEY_LOCAL_MACHINE\SOFTWARE\PragmaSystems\Interaccess\TelnetD\Users\ key that you want to use Full Pass Thru mode.

Fixes:

• PRB: Monitor Child Processes causes system crash
• PRB: Logging off interactive administrator causes sessions to lose console processing

Release Date: 2/16/01

Enhancements:

• New Monitor Child Process code to close session faster - better NTVDM cleanup
• Now allows large number of sessions, without using the "allow service to interact with desktop" for InetD service

Fixes:

• PRB: Session Limit reached, when "Allow Only Configured Groups Access" checked 
• PRB: TIMING MARK command from Symbol handhelds, causes increase in CPU usage

FIX: Configured Default Terminal Type will now override an UNKNOWN terminal type negotiation 

FIX: Login String Buffer exceeded error for Terminal Type prompt 

FIX: Denial of Service vulnerability issue

FIX: Session limit being reached early due to resource limits 

FIX: InterAccess Manager leaving orphan users in user list

FIX: Conflict with Server Heartbeat with UNIX clients 

FIX: Conflict with Server Heartbeat and IdleSessionTimeout - both features may now be used 

FIX: IAC EC handled correctly 

FIX: Backspace in Stream Mode will not erase characters in prompt

------ ENCRYPTED SESSIONS ONLY AVAILABLE WITH UNLIMITED CONNECTION VERSION 

Improved encryption. Encryption support is built with Microsoft's Crypto system built within Windows NT/95/98. It uses RSA industry standard 40-bit or 128-bit encryption algorithms for the tightest security available. 

Encrypted session negotiated between server and client. Start an encrypted session by adding the /N parameter to the telnetc command. Adding a /E to the TelnetD Server service, under InetD Configuration, will specify encrypted sessions only. 

FIX: Domains or usernames of configured users can include an underscore 

User can select the location of a TelnetD environment variable, if the variable already exist as a system variable

FIX: Deleting token from Access Control List. Solves problem of with a NEW user logging on after a large number of logons, not being able to run programs. 

User can modify the greeting message manually with the special characters \n, \r, and \t. \r\n should be used to specify a newline in greeting. 

Greeting messages can be up to 1024 characters. 

Multple printers can be captured simultaneously by the Console Telnet Client. Check the telnetc.txt file for more information. 

FIX: Cleaner server disconnect to prevent clients from getting a Connection Reset error 

Naming of configured TelnetD Users now allows local users to be named with or without the computer name 

PCTERM renamed to PragmaTerm so as not to conflict with WYSE PCTERM emulation 

New viewses.exe program that enables you to watch a telnet session as it occurs.

Console Registry Edit utility shipped with TelnetD. Use it to configure TelnetD in a telnet session. Changes will apply to new telnet sessions. 

Modified GUI(IMGR.EXE) configuration program to support all new features. 

 InetD now has an option to launch GUI applications. 

Session Logging, this feature will log all remote user sessions to individual files. Options for logging to plain text and HTML format. This will track user logon, logoff and all typing done by remote user.

**************** Special note about new features below: Although we explain how to change settings through the registry editor, all changes can now be performed through our GUI configuration application. ************************************************************* 

New screen scraper routine available. To enable this option you create a new value called "AdvancedScreenScraper" in the "HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD\\%USERNAME%" key. Replace %USERNAME% with the user you wish to use this option. If you have no telnetd users configured, place under the Default user key. Note: This option does not do any 24/25 line mapping. Therefore, if your client is set to only 24 lines that is all you will see. If you use the default Windows telnet client, we recommend that you set the lines to at least 26 in this mode. 

New PacketSize option in user configuration. This variable allows you to specify the largest packet size sent to the client. This allows the user to optimize data transfer rate for connections on Modems to a T-1. To enable this option you create a new value called "PacketSize" in the "HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD\\%USERNAME%" key. Replace %USERNAME% with the user you wish to use this option. This is a string value. To use the default packet size set it to 0. 

Option for slow clients(like hand helds) or slow connections. To enable this option you create a new value called "SlowConnection" in the "HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD\\%USERNAME%" key. Replace %USERNAME% with the user you wish to use this option. Note: This option will turn the client cursor off and when used with AdvancedScreenScraper option below it will only display in Monochrome. 

New Console Client Telnet heartbeat option. Option is /H N where N is a number of seconds to tell the server to send heartbeats to client. 

New Console Client Telnet UNIX option /X. This is useful when you run the Telnet Server in Stream Mode and your application only sends CR and not CRLF(carriage return, line feed), like ported UNIX applications.

Heartbeat option now available in server. On the server you create a new value called "ServerHeartBeat" in the "HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD" key. The value should be of type REG_SZ and should be a number representing seconds between heartbeats sent to the client. This option is very useful in situations where the client computer loses power and the connection is lost. In this situation WinSock does not always recognize the connection as lost and therefore the server believes the connection is still good.

Known issues with TelnetD Server

Users must have "Logon Locally" access right to access telnet server. 

In order for printing to work, users that wish to print must have Change access to the SpoolDir. 

The most common issues with User Configuration errors occur when the user that is trying to logon does not have correct permissions in the registry. Look at this area closely, it is probably a good idea to give Everyone at least query access to the PragmaSystems Registry. 

Java Telnet Client requires JAVA runtime 1.1 or later. You need at least Internet Explorer 4.01 for it to work correctly. - Java Telnet Client is VERY VERY SLOW! It also has some screen redraw problems and is not very useful currently. If you are not proficient in the ways of JAVA, DO NOT try and run the Java Client. 

Console Telnet Client is slow on Windows 95. To speed it up you should :
1.) Enable all "Shadow RAM" on your computer, this is a BIOS configuration option.
2.) Run in FULL SCREEN! This is a must in Windows 95, otherwise you will be disappointed with the performance.
3.) Although the Console Telnet Client is a 32-Bit Win32 application, lowering the "Idle Sensitivity" setting for MS-DOS programs does seem to help. 

Console Telnet Client does not support a console window that has a scroll buffer if you are using Full Console Mode with the TelnetD Server. 

Console Telnet Client does not support long printer names, that means a printer name with spaces in the name.

More performance enhancements!!! 

Idle Session Timeout is now used during logon. The Default users setting for Idle Session Timeout will be used for the logon process. 

ALT Key Re-Map Default has been changed from ESC key to CTRL-A. When a program requires that you send an ALT key sequence, we used to use ESC as the ALT key mapping. This caused you to press the ESC key 2 times for ESC to work. This feature has always been configurable. However, after many complaints(We really do listen) about this default setting, we have decided to change it to CTRL-A. This setting is in the User Configuration and you will see a value of 1, CTRL-A is sent as a 1. If you liked the ESC key mapping, change the value to 27(value sent for ESC key).

Shell Initializer is now passed as a parameter to your command shell. Many command shells require that you specify a switch for this to work properly, for example CMD.EXE requires either a /C or /K switch. 

Better WYSE-50 support, now works in Full-Console Mode. 

More Security!!!! You can now specify NT Server groups for access to telnet. This is based on individual \\Server groups. This means that the group name can cross PDC boundaries, as long as the server is reachable through your network. 

You can now specify the user logon information to TelnetD on command line. To configure this option, you setup an InetD service to launch the TelnetD process. We recommend that you remove Read Access from the InetD registry tree for all users except System Account and Administrators. Accepted parameters are: /U username /P password /D domain. Using your Registry editor, goto HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD and change the Value for LogonType to 0. NOTE: This option does NOT PROVIDE ANY SECURITY. It is highly recommended that you change the port in which telnetd is launched to anything other than 23. 

Registry option to turn off the Network cleanup code. This may be needed for systems using Netware connections. If you notice that all Netware drive mappings are unmapped after a telnet session is closed, this is for you. Using your Registry editor, goto HKEY_LOCAL_MACHINE\\Software\\PragmaSystems\\InterAccess\\TelnetD and set the value for NetworkCleanup to no.

Performance increase. 

Network drive cleanup. Any drives that are mapped in a telnet session will now be unmapped upon exit of telnet session. 

New "Monitor Child Process" code that works on all platforms. It is now recommended that you always have "Monitor Child Process" option turned on. The only time you should turn off this option is to spawn programs from telnet that you wish to continue running after session is complete. 

Added RSHD and REXECD Server services. You can use the Windows 95/NT rsh.exe or rexec.exe clients. 

Support for canceling a telnet print job from client by pressing CTRL-c. If you have a print job being routed to your client you and you wish to cancel that job, simply press CTRL-c in your client session. Note: Most printers have a buffer to which data is stored before being printed, in this case your printer will not stop until that buffer is empty. 

Fixed a problem with the printer service dropping characters. 

Home Directory setting on a per user basis. This option overrides settings in the NT User Profile. 

Default terminal type setting on a per user basis. If your client does not report a terminal type or you simply do not want to be bothered by the terminal type prompt, you can use this setting. 

Fixed problem with CONTROL-c sequence and Emacs editor. 

Added new Monitor Sessions option. This setting allows you to see what users are doing in their sessions as they work. You must start the InetD service as "Interact with Desktop" type of service. Then, whenever a session is started you will see that user's session on the Server. You must be logged onto the server to see the sessions. Note: This feature is not set by the GUI configuration program. You must use your registry editor and change the \\SOFTWARE\\PragmaSystems\\InterAccess\\TelnetD\\MonitorSessions value to yes. In the near future we will make an option to monitor any session at any time.

Graceful Application Termination. In case of a link or remote PC failure we will gracefully terminate the executing application, therefore saving important data that may otherwise be lost or corrupted. This is supplied on a per-user and per-application basis. That means you can configure different terminate strings in each of your configured TelnetD Server user profiles. We have created these special character sequences to be used with the termination strings. ESC ENTER ALT CTRL SHIFT F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 SLEEPX ( X is replaced with a number, also SLEEP must be upper case) Here are some examples: To send sequence CONTROL ALT x: CTRL-ALT-x To send the word: hello h,e,l,l,o,ENTER To send sequence CONTROL ALT Function Key 4: CTRL-ALT-F4 To send the above, then sleep for 5 seconds and send "exit": CTRL-ALT-F4,SLEEP5,e,x,i,t,ENTER 

Environment variables for every configured TelnetD User. Through our GUI configuration program you can set environment variables on a per-user basis. The environment variables will be either appended to the existing variables or new ones can be created. This will make life very easy for Administrators of the TelnetD systems, you can manage user environments through our GUI from any other NT or Windows 95 system. (Instead of trying to manage a bunch of batch files you can use a nice friendly GUI) 

Added the ability to create a new user by copying an existing user settings in the User Configuration program. 

Z-Modem file transfer programs, sz.exe and rz.exe. With these files and a client that supports Z-Modem you can send or receive files in your telnet session. No need to switch over to FTP or anything else to transfer files. 

Console Telnet Client now supports Z-Modem file transfers. 

We are now shipping ps.exe(Process Viewer) and kill.exe(Kill Process) with the base products.

Silent installs can be performed by running the setup.exe file with a -s option For Windows 95: the option -f1"full path\setup95.iss" needs to be added, including the quotation marks. To change the directory, folder name, or component selection, the setup.iss (or setup95.iss) file needs to be changed. It can be modified using a text editor. It needs to be in the same directory as setup.exe. To remove a component, remove the component and sub-component listing in the response file under the heading [SdComponentDialog2-0]. Be careful to remove all references to the component. To change the destination directory change the value of szDir under the heading [SdAskDestPath-0], or for Companion under the heading [SdAskDestPath-1]. To change the group folder change the value szFolder under the heading [SdSelectFolder-0], or [SdSelectFolder-1] for Companion. Modify the interact.ini file located in the same directory as setup.exe to change InterAccess Manager settings during install. The shipping interact.ini file contains all the default settings defined, but commented out. To set a different value during install, for settings that have finite possible values remove the comment designator (#) of the new setting. For settings that can have any value, such as a numeric value, remove the comment designator (#) and changed the value after the = sign. By removing the comment on the default value, the user is assured of installing the default value no matter what the setting might be on a previous version. InetD Services can be added by adding a full section with the heading [InetD - Servicex], where x is a number less than 10. See the example InetD services that are in the interact.ini file. The silent install will detect if a previous version is installed, if so it will automatically install to that directory. * To run a silent install from the self-extracting executable, the executable must be run and extracted to a folder. Cancel the install process, then run the setup.exe as described above.

Secured(Encrypted) LOGON. You now have 2 choices for your logon security.
1.) Plain/Clear Text which is the Telnet standard.
2.) Secure Logon, uses encryption for Logon Parameters. 
The Secure Logon feature is only supported when connecting to TelnetD with Pragmas Console Telnet Client. No special configuration is needed on the server, the client is giving a command lines parameter, "/S", that tells it to connect with the server and send encrypted logon information. You can configure the server so that it will only accept secure logons, this is done through the "Configure TelnetD" icon on the Server. 

Console Wrapper Version 2.0. This allows any console application to run in a telnet session. Applications like VIM, NT Resource Kit's applications (PMON, VI, etc.), Computer Associates Open Ingres SQL Server command line tools and REALLY any other console application. * This version will not work with TelnetD Release 3.0 

Print Monitor. Allows telnet session print jobs to be sent back through to the telnet client. Very useful for POS systems. The user prints with their application and the job will be sent back to the client and can then be routed to the local printer or any other printer accessible by the telnet client application. 

Multiple User Configuration. Almost all of the Telnet Session configuration can be specified on a per user basis. 

Only allow the users configured with above feature to log on to your TelnetD Server. Very useful for securing your Telnet Server and controlling who is allowed to logon. 

Created PRAGMASYS_TELNETD_PID environment variable. This allows the user to know what Process Id his/her telnet session is using. 

Created Named Mutex Semaphores for blocking TelnetD Server socket I/O, can be used by developers writing code to run in a telnet session and need full control of the TCP/IP socket. The Input or Reading Semaphore is named TelnetDInputXXXMutex, where you replace XXX with the PRAGMASYS_TELNETD_PID environment variable. The Output or Writing Semaphore is named TelnetDOutputXXXMutex, where you replace XXX with the PRAGMASYS_TELNETD_PID environment variable. 

All user environment variables are now imported from NT for logged on user. 

4 Gray Scale support for WYSE Monochrome Terminals. 

Better error messaging, both in Event Log and Errors displayed to the end user.

IP Address Filtering. Enables you to Deny or Grant access to the InetD services(TelnetD, Telnet Manager, Run As, and any of your services that InetD is used to launch) by the client IP Address. 

InetD Service Logon. You can now give logon information for any of the InetD services(TelnetD, Telnet Manager, Run As, and any of your services that InetD is used to launch) and that program will run as that user. 

Changes to make InetD faster and also report better error messages.

Telnet Clients are now included. Console Telnet Client and Java Client.

Configuration and Management applications have been combined into one program called "InterAccess Manager"(IMgr.exe). Support for managing and configuring any of the InterAccess Products(TelnetD, InetD, Terminal Server, Companion) is available through this one application. This application can be run on any Windows NT or Windows 95 machine to configure and manage your InterAccess Products across your network. See the online help for more information on InterAccess Manager. 

InterAccess Manager is connection oriented. Information is refreshed automatically as soon as a Telnet session is established with the Server you are managing. 

New RunAs InetD Service. This application is useful for persons that need the NT Logon Security of our Telnet Service but without the Telnet Service. After Logon, RunAs allows you to launch any of your programs in the context of who you logged on as. RunAs will also run without a network connection by simply typing runas. 

Telnet Diagnostics(NOT YET AVAILABLE). A new program that can assist with supporting the TelnetD Server. If by chance you have any problems with our InetD or TelnetD Server, this program can help to determine what is wrong.