Configured Connection

To create a new connection

1. Click the New Telnet Connection icon ( ).

The New Telnet Connection Settings dialog box appears.

2. Click Configured > New.

The Connection Settings dialog box appears.

3. On the Telnet tab, enter values in the Host, User ID, and Password boxes. These are required fields.

4. Retype the password in the Retype box.

5. Select Save Password to save your password on the Eclipse for future use of the same host account.

6. Select either OS 2200 or UNIX as the target operating system.

7. Type a name for the account in the Connection Name box. The name is displayed in the Telnet wizard.

8. Change the default values in the Port Number and Character Conversion boxes, if required.

9. Select the SSL Port check box if you want a Secure Sockets Layer (SSL) Telnet connection. Refer to SSL Telnet Connections for more information.

10. Select the MHFS (Multi Host File Sharing) check box, if the system has MHFS support.

11. To create login scripts automatically, click Record and answer the questions. Refer to Automatically Creating Login Scripts for information on how to record scripts.

The values appear in the Host Prompt and Response boxes, as shown in the following figure:

12. To create login scripts manually, click Add and enter host prompts and responses.

13. To move an entry earlier or later in the script, select the entry and click Move Up or Move Down.

14. To remove an entry or group of entries, select one or more entries and click Remove. 

15. To edit an entry, select the entry and click Edit.

When you modify the entry in the editing field, the Add button changes to Replace and the other buttons   are disabled. Click Replace to put the edited entry in the list. Disabled buttons are then enabled and the  Replace button changes to Add.

16. If the CIFS login information is different from the Telnet login information, click the CIFS tab and make the required changes.

Note: Values entered for the Telnet login are duplicated for the CIFS login. You can change any values on the CIFS tab as needed, including the host. The CIFS tab, however, does not offer an operating system selection.3. Type the new password and type it again in the Retype box.

17. Click OK.

Note: Due to security improvements in Windows 7 and later, NTLM v2 is used to authenticate the credentials with an OS 2200 system. Unlike NTLM v1 used by Windows XP, NTLM v2 does not automatically convert CIFS passwords to uppercase. Therefore, passwords are case-sensitive.

While migrating from Windows XP, users must enter the password in the same case as used by the OS 2200 administrator while creating a password. By default, passwords are in uppercase on the OS 2200 system.

SSL Telnet Connections

OS 2200 IDE for Eclipse supports Telnet connections to Secure Sockets Layer (SSL) Telnet on the OS 2200 system. The following interfaces are involved in SSL Telnet:

• The certificate from the OS 2200 system and its storage

An SSL server has a certificate that states that the server is who it says it is, which identifies the server.

• The indication to the Telnet client that the target host and port support Telnet

The certificate is verified automatically or the client accepts the certificate. The client continues to use the usual userid and password credentials. The difference is that, once the client accepts the certificate, all traffic is encrypted.

Certificates can be obtained in the following ways:

• By a Trusted Certificate Authority (CA), either a third party CA (such as VeriSign™ ) or a CA within user's organization

• By a local untrusted CA, or a self-signed certificate using tools such as OpenSSL. 

If the service side certificate cannot be verified because the certificate is self-signed certificate or the certificate is expired, the user receives a New Certificate Presented dialog box. Read the message on the Message tab, peruse the certificate on the View Certificate tab, and then if you wish to accept the certificate, click Accept Certificate to continue the connection.

Once the client accepts the certificate, the OS 2200 system stores the certificate and makes the connection. The credentials still need to be verified (and given initially, if this is a raw Telnet login). Once the SSL connection is established, all the traffic, including the credentials, will be encrypted.

If the user clicks Deny Certificate or dismisses the window, the certificate is not stored and the connection is not made.

Note: ClearPath 14.0 release includes the CPComm version 6R3. This version of CPComm does not recognize SSLV2ClientHello. Hence, from Eclipse-2200 version 3.7.2 onwards, the default protocol would be SSLv3. Eclipse-2200 version 3.7.2 can be used with the previous releases of ClearPath. If the OS 2200 server at the customer site has ClearPath 14.0 installed, it is recommended to make use of Eclipse-2200 version 3.7.2 or later to have the Telnet connection established over SSL.