Table of Contents Chapter 1 Introduction Chapter 2 Enhancements and Changes Chapter 3 Documentation Updates Chapter 1 Introduction These Release Notes describe the changes and enhancements made to the MultiNet product in version 4.4. This chapter describes conventions used in the MultiNet documentation set and the various methods to contact and receive technical support. o For information about product changes and enhancements in the MultiNet V4.4 Consolidated Distribution, refer to Chapter 2 of these release notes. o For information about changes to the documentation set, refer to Chapter 3 of these release notes. Obtaining Technical Support Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained MultiNet from an authorized distributor or partner, you receive your technical support directly from them. You can contact Technical Support by: o Sending electronic mail (Sending Electronic Mail) o Calling Technical Support (Calling Technical Support) o Faxing a description of your problem to the Technical Support Group (Contacting Technical Support by Fax) Before Contacting Technical Support Before you call, or send email or a fax: o Verify that your Maintenance Service Agreement is current. o Read the online Release Notes completely. o Have the following information available: o Your name o Your company name o Your email address o Your voice and fax telephone numbers o Your Maintenance Contract Number o OpenVMS architecture o OpenVMS version o MultiNet layered products and versions o Have complete information about your configuration, error messages that appeared, and problem specifics. o Be prepared to let a Development engineer connect to your system either with TELNET or by dialing in using a modem. Be prepared to give the engineer access to a privileged account to diagnose your problem. You can obtain information about your OpenVMS architecture, OpenVMS version, MultiNet version, and layered products with the MULTINET SHOW /LICENSE command. Execute the following command on a fully loaded system and email the output to support@process.com: $ MULTINET SHOW /LICENSE Process Software MultiNet V4.4, VAXstation 4000-90, OpenVMS VAX V7.1 In this example: The machine or system architecture is VAX. The OpenVMS version is V7.1. The MultiNet version is V4.4. Use Table 1-1 as a template to record the relevant information about your system. Table 1-2 System Information Required Information Your System Information Your name Company name Your email address Your voice and fax telephone numbers System architecture VAX | Alpha OpenVMS version MultiNet version Please provide information about installed MultiNet applications and patch kits, by sending a copy of MULTINET:MULTINET_VERSION.; file. Sending Electronic Mail For many questions, electronic mail is the preferred communication method. Technical support via electronic mail is available to customers with a current support contract. Send electronic mail to support@process.com. At the beginning of your mail message, include the information listed in Before Contacting Technical Support. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request. Electronic mail is answered within the desired goal of two hours, during our normal business hours, Monday through Friday from 8:30 a.m. to 5:00 p.m., United States Eastern Time. Calling Technical Support For regular support issues, call 800-394-8700 or 508-628-5074 for support Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your Account Representative for further details. Before calling, have available the information described in Before Contacting Technical Support. When you call, you will be connected to a Technical Support Specialist. Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system. If our Support Specialists are assisting other customers and you are put on hold, please stay on the line. Most calls are answered in less than five minutes. If you cannot wait for a Specialist to take your call, please take advantage of our automatic call logging feature by sending email to support@process.com (see Sending Electronic Mail). Contacting Technical Support by Fax You can send fax transmissions directly to Technical Support at 508-879-0042. Before faxing comments or questions, complete the steps in Before Contacting Technical Support and include all your system information at the beginning of your fax message. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your fax support request. Faxed questions are answered Monday through Friday from 8:30 a.m. to 7:00 p.m. United States Eastern Time. Obtaining Online Help Extensive information about MultiNet is provided in the MultiNet help library. For more information, enter the following command: $ HELP MULTINET MultiNet Frequently Asked Questions (FAQs) List You can obtain an updated list of frequently asked questions (FAQs) and answers about MultiNet products from the Process Software home page located at http://www.process.com. Choose the "Support" link to access useful information on FAQs and patch ECOs. Accessing the MultiNet Public Mailing List Process Software maintains two public mailing lists for MultiNet customers: o Info-MultiNet@process.com o MultiNet-Announce@process.com The Info-MultiNet@process.com mailing list is a forum for discussion among MultiNet system managers and programmers. Questions and problems regarding MultiNet can be posted for a response by any of the subscribers. To subscribe to Info-MultiNet, send a mail message with the word "SUBSCRIBE" in the body to Info-MultiNet-request@process.com. The information exchanged over Info-MultiNet is also available via the USENET newsgroup vmsnet.networks.tcp-ip.multinet. You can retrieve the Info-MultiNet archives by anonymous FTP to ftp.multinet.process.com. The archives are located in the directory [.MAIL_ARCHIVES.INFO-MULTINET]. You can also find the Info-MultiNet archives on the MultiNet consolidated CD- ROM in the directory: [INFO-MULTINET] The MultiNet-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to MultiNet (patch releases, product releases, etc.). To subscribe to MultiNet-Announce, send a mail message with the word "SUBSCRIBE" in the body to MultiNet-Announce-request@process.com. Process Software World Wide Web Server Electronic support is provided through the Process Software World Wide Web server, which you can access with any World Wide Web browser; the URL is http://www.process.com (select "Support"). Obtaining Software Patches Over the Internet Process Software provides software patches in save set and ZIP format on its anonymous FTP server, ftp.multinet.process.com. For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches. To retrieve a software patch, enter the following commands: $ MULTINET FTP /USERNAME=ANONYMOUS/PASSWORD="emailaddress" FTP.MULTINET.PROCESS.COM A message welcoming you to the Process Software FTP directory appears next followed by the FTP prompt. Enter the following at the FTP> prompts: FTP.MULTINET.PROCESS.COM>CD [.PATCHES.MULTINETxxx] FTP.MULTINET.PROCESS.COM>GET update_filename In these commands: o emailaddress is your email address in the standard user@host format. o xxx is the version of MultiNet you want to transfer. o update_filename is the name of the file you want to transfer. To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an intermediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system. In addition, if you extract the patch from the distribution zip file on another system when FTPing the patch, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS system: o If you use the GET command to download the file from the intermediate system, use the FTP RECORD-SIZE 2048 command before transferring the file. o If you use the PUT command to upload the file to your OpenVMS system, log into the intermediate system and use the FTP quote site rms recsize 2048 command before transferring the file. Process Software also supplies UNZIP utilities for OpenVMS VAX and Alpha for decompressing ZIP archives in the [CONTRIBUTED- SOFTWARE.APPLICATIONS.ZIP] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use the UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory: $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your MultiNet system with the software patch. Documentation Comments Your comments about the information in these Release Notes can help us improve the documentation. If you have corrections or suggestions for improvement, please let us know. Be as specific as possible about your comments: include the exact title of the document, version, date, and page references as appropriate. You can send your comments by email to: techpubs@process.com or mail them to: Process Software 959 Concord Street Framingham, MA 01701-4682 Attention: Marketing Manager You can also fax your comments to us at 508-879-0042. Your comments about our documentation are appreciated. CD-ROM Contents The directory structure on the CD is as follows: [MULTINET044] MultiNet Kit [DOCUMENTATION] HTML format (.html) PDF format (.pdf) PostScript format (.ps) TEXT format (.txt) MULTINET044.RELEASE_NOTES [INFO-MULTINET] [RFCs] [BINDDOC] [XPDF] [XPDF.AXP] for Alpha images [XPDF.VAX] for VAX images [XPDF.DOC] for XPDF documentation [LYNX] [LYNX.AXP] for Alpha images [LYNX.VAX] for VAX images [VAX55_DECC_RTL] Online Documentation The MultiNet documentation set is available on the product CD in PDF, text, PostScript, and HTML formats. PDF Format The MultiNet documentation set has the following PDF files: Installation & Administrator MULTINET_ADMIN_GUIDE.PDF Administrator Reference MULTINET_ADMIN_REFERENCE.PDF Messages, Logicals, & DECnet Apps MULTINET_MESSAGES.PDF Programmer Reference MULTINET_PROGRAMMERS_REFERENCE.PDF User Guide MULTINET_USER_GUIDE.PDF Master Index MULTINET_MASTER_INDEX.PDF The PDF format is readable from a PC, a VAX, or an Alpha system. There is a PDF reader on the CD for each platform. o Use Acrobat Reader to read the PDF files from a PC. Your PC must have 386 architecture or later to use Acrobat Reader. You can get Acrobat Reader from Adobe Systems website: www.adobe.com. It is free! o Use the XPDF Reader (found in the [XPDF] directory on the CD) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader XPDF_AXP.EXE. The [XPDF.VAX] directory contains the VAX architecture reader XPDF_VAX.EXE. Note! The XPDF Reader does not work on a PC. PCs running the Windows or NT operating system cannot read Process Software's CD. You cannot load files from the MultiNet CD directly to a PC. Load them to your VAX or Alpha machine, then transfer them to your PC. To read the MultiNet CD on a PC, load the files to your VAX or Alpha machine, then transfer them to your PC. We suggest using FTP to transfer these files. The following is an example using MS-DOS: C:> ftp node ftp> binary ftp> mget cd:[documentation.pdf] In addition, Process Software has included LYNX, the character-cell web browser for VMS. It is in the [LYNX] directory on the CD. Using Acrobat Reader To read the PDF files using Acrobat Reader: 1. Double click Acrobat Exchange. 2. Choose Open from the File menu. 3. Select the .pdf file you want to open. 4. Use the menu bar at the top of the screen to navigate the document or click a Table of Contents entry (on the left) to go directly to that information. Hints: The binocular icon opens search functions. The magnifying glass icon enlarges the text and llustrations. Using XPDF Thanks to Derek B. Noonburg for letting us download his XPDF application. Note! You need a three-button mouse to use XPDF. At the DCL prompt from the directory in which XPDF_VAX.EXE or XPDF_AXP.EXE is stored, do the following: 1. Type RUN XPDF_VAX.EXE or RUN XPDF_AXP.EXE. The XPDF screen appears. 2. Position the arrow on any of the icons (except the ? icon) on the bottom of the screen. 3. Press the right mouse button to display choices. 4. Select OPEN to display the list of PDF files. 5. Select the PDF file you want and click OPEN to read the file. 6. Use the icons on the bottom of the screen to search for the information you want. To view the online help for XPDF: 1. Position the cursor on the question mark (?) icon. 2. Press the left mouse button to open the online help. HTML Format Online documentation is available as HTML files you can use either with a PC browser or with a character cell browser. The documentation files and their contents are listed next. Document Directory Title Installation and Administrator's Guide ADMIN_GUIDE User's Guide USER_GUIDE Administrator's Reference ADMIN_REFERENCE Programmer's Reference PROGRAMMERS_REFERENCE Messages and Logicals MESSAGES PostScript Format Documentation is available in the following PostScript files. Document Name PostScript File Names Installation and Administrator's MULTINET_ADMIN_GUIDE.PS Admin Reference MULTINET_ADMIN_REFERENCE.PS Programmer's MULTINET_PROGRAMMERS_REFERENCE.PS User's Guide MULTINET_USER_GUIDE.PS Master Index MULTINET_MASTER_INDEX.PS Messages, Logicals, and DECnet Apps MULTINET_MESSAGES.PS Chapter 2 Enhancements and Changes This chapter describes the enhancements and changes made for MultiNet V4.4. Mandatory VMS Patch o The patch kit VAXCDU01_061, or its successor, from Compaq Computer Corporation must be installed for OpenVMS VAX V5.5-2 through V6.1 in order for MultiNet V4.4A to install. Without this patch the following error message displays while installing MultiNet V4.4A: %DCU-F-INTNODESPACE. Internal error: Node space exhausted Disabled Services IP AddressWorks Process Software no longer supports IP AddressWorks. There are no IP AddressWorks components in this kit and IP AddressWorks has not been tested with this version of MultiNet. RSA RSA ACE/Agent for OpenVMS is no longer supported by RSA Security. Therefore, Process Software can no longer assist with RSA ACE/Agent for OpenVMS-related problems. Process Software recommends using SSH instead. Known Problems IMAP If RFC822 message headers have been placed at the end of a mail message by the SMTP server, IMAP may not retrieve messages properly. An ECO will be forthcoming to correct this problem. (D/E 6997) SCP2 The version of SCP shipped with OpenSSH's software uses the SSH1 protocol for file transfer. Process Software's MultiNet only supports file transfers using the SSH2 protocol. Using OpenSSH's scp may result in the following bugcheck from the MultiNet SSH server: %%%%%%%%%%% OPCOM 17-DEC-2001 16:59:27.26 %%%%%%%%%%% Message from user SYSTEM on FLOWER %SSHD 0007-E-FATAL ERROR: Bugcheck: failed to find record for descriptor 4 Process Software does not support OpenSSH but we are committed to providing you with information that will assist you in making the correct decision for your TCP/IP requirements. Logical Name Changes Additional documented logical names: o Some graphical display FTP clients expect the output of directory commands to be in a UNIX system format. To enable this UNIX format, use the following either at the system level or in the user's LOGIN.COM: $ DEFINE MULTINET_FTP_DISALLOW_UNIX_STYLE FALSE and $ DEFINE MULTINET_FTP_UNIX_STYLE_BY_DEFAULT ANYTHING Enhancements CONFIG/INSTALL o MULTINET:HOSTS.SERVICES has been updated to make the service entries more modern. You may need to remove any local definitions of services now included in HOSTS.SERVICES. DHCP Client o The DHCP client is new to MultiNet beginning with V4.4. It resides on the client host and sets the network configuration dynamically. The MultiNet DHCP client communicates with a DHCP server to get an IP address and other configuration information. The DHCP client uses this information to configure the network parameters of the host and to start/restart the network. If you choose not to enable the DHCP client on the host, you configure MultiNet as usual. If you choose to enable the DHCP client on the host, the DHCP client configures the IP address, the Domain name, the DNS server name, the route/gateway, etc. for you. Remember, you must have a DHCP server (v3 or later) on the network when using the DHCP client. Open the file MULTINET:DHCLIENT.DB to view query information from the DHCP server. The last lease entry at the end of the file contains the most recent information obtained from the DHCP server. DNS o MultiNet's DNS has been upgraded from BIND 8.2.3 to BIND 8.2.4. FTP o Added Session Accounting MultiNet can record accounting information from services that have been enabled. Currently this includes FTP and SMTP. The accounting information includes when a network session took place and how much data was transferred. The accounting facility is enabled in the following manner: $ MULTINET CONFIG/SERVER ENABLE ACCOUNTING EXIT Look at MULTINET:ACCOUNTING.CONF for additional configuration information. The format of the accounting records is described in MULTINET_ROOT:[MULTINET.EXAMPLES]ACCOUNTING.H. FTP Accounting can be configured using the following commands: $ MULTINET CONFIGURE/NETWORK SET FTP-ACCOUNTING-HOST name SET FTP-ACCOUNTING-PORT number WRITE EXIT The collected accounting information can be displayed with the MULTINET ACCOUNTING command. o A sample program for processing the accounting data is in MULTINET_ROOT:[MULTINET.EXAMPLES]ACC_DUMP.C IMAP o The IMAP global options found in the IMAPD.CONF file are now recognized. (D/E 6997) o Added a logical MULTINET_IMAPD_MESSAGE_ONE that can be used to define the text IMAP will send to user when a mail message cannot be retrieved. (D/E 7429) o Added a logical "MULTINET_IMAPD_MESSAGE_SIZE_LIMIT" which can be used to limit the size of the mail message that IMAP processes. (D/E 7430) o The amount of messages to log to the console has been reduced by disabling auditing when updating uaf. (D/E 7456) IPP Print Symbiont o The IPP print symbiont is an OpenVMS print symbiont working with the OpenVMS printing subsystem to implement an IPP client. It allows printing over a network to printers and servers that support the IPP v1.0 network printing protocol. The user interface is similar to other print symbionts in that it uses PRINT commands or system library calls to submit jobs to print queues. The IPP protocol has specific qualifier values and queue settings that must be present to allow the symbiont to function. o Added these qualifiers: /FINISHINGS="Staple, Punch, Cover, Bind" /JOB_PRIORITY=num /MULTIPLE_DOCUMENT_HANDLING=value /MEDIA=name /PAGE_RANGES="range [, range]..." /QUALITY=keyword Note! The values that can be specified with each of these additions are the same as for the associated PRINT command qualifier. That is, "COPIES_DEFAULT" takes an integer the same way that "/COPIES" does, and "MEDIA_DEFAULT" takes a media name, the same way that "/MEDIA" does. o Added the capability to specify all PRINT command qualifier defaults in the queue configuration, so that they become defaults for the queue. o DEFAULT_DOCUMENT_FORMAT and DOCUMENT_FORMAT_DEFAULT are synonyms, and can be used interchangeably. o Added capability to specify document_format values using local equivalences from a file. For example, "PS" could be made equivalent to "application/postscript" to make it easier on users when it comes to memory or to typing. o Added an "escape mechanism" in case a local name is ever made into a different MIME- media-type. Prefixing the document format name with "%" prevents alias translation. "%PS" means "just send it as 'PS', don't translate "PS" into "application/postscript" in the request. o Added a template file (DOCUMENT_FORMAT_ALIASES.DAT in the product home directory) with some standard aliases both as an example and as a simple default translation file. o To use document format name translation, define the system logical name "MULTINET_IPP_DOCALIAS_FILE" with the filename of the alias file as the equivalence string. o The format of lines in the alias file is: Mime-name: alias, alias, alias... Blank lines are ignored, and lines starting with "#" are treated as comments and ignored, too. o Modified the config logical checks to make the global logical be in addition to the queue specific one, rather than instead of it. o The queue-specific logical is parsed second allowing for an override of the global settings on a queue-by-queue basis when that behavior is desired. o The IPP_SHOW utility allows you to get the capabilities supported by an IPP server and to display them in an easy to read, easy to parse, or DCL symbol format, with optional output to a file. The program could be used by humans to see what a given server supports, by a program to gather information about a number of printers, or by a DCL or other program to check the capabilities of a given server before submitting a print job to a queue. The command syntax is: $ MULTINET IPP SHOW server_URI /qualifiers.... LDP Server o The MultiNet LPD server no longer fails with a "Failed to rename file from xxx to yyy" error when the job control file contains multiple entries of the same file name. (D/E 7075) o The MultiNet LPD server no longer prepares to receive the file data when the overflowed data file size is received from an LPD client. (D/E 7501) LPD Symbiont o An intermittent "Illegal remote printer specifier" error has been fixed. (D/E 7276, 7349) o Support has been added for the new MULTINET_LPD_SYMBIONT_FILE_SIZE_CHECK logical that gives the LPD symbiont the ability to compensate for LPD printers which do not properly handle zero- size files. (D/E 4360) To enable this feature, define the following logical: $ define/sys/exe MULTINET_LPD_SYMBIONT_FILE_SIZE_CHECK TRUE MAIL-CONFIG o The following commands have been added to the list of commands that can be entered from the MAIL-CONFIG prompt which is accessed with the command $ MULTINET CONFIGURE /MAIL. SET RFC2789 - Enable the RFC2789 MIB table SET ACCOUNTING-HOST - Set the Accounting host for SMTP SET ACCOUNTING-PORT - Set the Accounting Port for SMTP SCP2 o SCP2 consists of two programs - the client program SCP2, which includes an embedded SFTP server for local file access, and SFTP-SERVER2, which runs on the remote system to access the file. SCP2 communicates with SSH2 for authentication and transport (which includes encryption) to remote systems, SFTP-SERVER2 communicates with SSHD2 for data transport. Secure Copy Protocol (SCP) is new to MultiNet V4.4. SCP file transfers are different from FTP file transfers. With FTP a file can be transferred as ASCII, BINARY, RECORD, or in OpenVMS format (if MultiNet is in use). In SCP there is one specified format - BINARY. Also, the defined syntax for a file specification is UNIX syntax. Due to these restrictions, files that are transferred from dissimilar systems may or may not be useful. Process Software has used methods available in the protocol to attempt to improve the chances that files will be useful upon transfer. SCP is an evolving specification, and some implementations may not support all options available in the protocol, or worse, not tolerate some optional parts of later versions of the protocol. Process Software has used the defined extensions in the SCP protocol to transfer information about the VMS file header characteristics such that when a file is transferred between two VMS systems running MultiNet v4.4, the file header information will also be transferred and the file will have the same format on the destination system as it had on the source system. Also, when a file is transferred to a non-VMS system, a method has been provided to translate those files that can be translated into a format that will be usable on the remote system. Files that are transferred from non-VMS systems are stored as stream files on the VMS system, which provides compatibility for text files from those systems. The SCP2 command accepts the /TRANSLATE_VMS qualifier with a list of values; possibilities are: ALL, NONE, VARIABLE, FIXED, and VFC. The default is =ALL. Basic testing for bad combinations of values is done, but the only error message is the "usage" statement (command syntax message). The qualifier is applied to the input stream, as part of the initialization message. No check is made as to whether or not it is a local source to allow it to work if you are copying from a remote VMS system to a remote non-VMS system. The server uses the logical MULTINET_SFTP_TRANSLATE_VMS_FILE_TYPES for the same thing. This logical is bit encoded: 1=FIXED, 2=VARIABLE, 4=VFC. (Note that the logical applies to SCP2 as well because SCP2 contains the server code.) Current SCP2 command syntax: SCP2 [[user@]host[#port]::]file [[user@]host[#port]::]file [switches] Switches: /VMS and /TRANSLATE_VMS are mutually exlusive /BATCH Start SSH2 in batch mode. /CIPHER=(cipher-1,...,cipher-n) Select encryption algorithm(s). /DEBUG=level Set debug level. /DIRECTORY Force target to be a directory. /HELP Display this help. /IDENTITY_FILE=file Identity file for public key authentication. /PORT Tell SCP2 which port SSHD2 listens on the remote machine. /PRESERVE Preserve file attributes and timestamps. /NOPROGRESS Do not show progress indicator. /QUIET Quiet; do not display any warning messages. /RECURSIVE Process entire directory tree. /REMOVE Remove source files after copying. /TRANSLATE_VMS=(ALL, NONE, VARIABLE, FIXED, VFC) Select VMS text files to be translated (default-ALL). /VERBOSE Display verbose debugging messages. Equal to "/debug=2". /VERSION Display version number only. /VMS Negotiate ability to transfer VMS file information. o Some ODS-5 file specifications are not properly parsed due to differences in the C RTL with how it handles ODS-2 and ODS-5 file systems. Updating the C RTL on your system does NOT change this, as the SCP2 image contains the C RTL routines that it uses. o SCP2 with /RECURSIVE and /VMS copies all versions of the files to the target system. o The default value for MULTINET_SCP2_CONNECT_TIMEOUT is two (2) minutes. SCP2 has been modified to try without /VMS if it times out with /VMS. A warning message displays when this happens. There is another two (2) minute timeout period for the try without /VMS. This results in successful copies to F-Secure servers, but not to Open-SSH servers which exit immediately when Open-SSH servers receive an initialization message that they do not understand. o When using the F-Secure Windows File Transfer client to copy a file to VMS, the first copy works fine. Subsequent attempts will fail displaying this message: Transfer failed with error 2: destination (/disk$sys_login/login/user) is not a directory. The reason is due to the client using a different string on the second attempt that the VMS implementation can not recognize as a directory specification. Process Software will be working with F-Secure to attempt to resolve this problem. Note that subsequent uploads require exiting and restarting the F-Secure client application. SMTP o Added Session Accounting. See FTP above for more details. SMTP Accounting can now be configured with the following commands: $ MULTINET CONFIGURE/MAIL SET RFC2789 ! Enables the RFC2789 MIB table SET ACCOUNTING-HOST name ! Set the Accounting host for SMTP SET ACCOUNTING-PORT number ! Set the Accounting port for SMTP SSH o The client and the server have been updated to support versions 1 and 2 of the SSH protocol. The client and server together, using the Diffie-Hellman key-exchange method, determine a 256-bit random number to use as the "session key". This key is used to encrypt all further communications in the session. The multiple encryption algorithms supported by SSH v2 are 3DES (the default), TWOFISH, BLOWFISH, DES, CAST-128, and ARCFOUR. SSH v2 offers the following server system authentications: host-based, public-key, and password. o For OpenSSH client users: when using public-key authentication for the OpenSSH client, the key file record format must be either STREAM-LF or 512-byte fixed. If the key file is in VARIABLE format, the server will be unable to read the key file successfully, with the result that public-key authentication will fail. You need to convert the key created by OpenSSH to the SECSH Public File Format. See the OpenSSH documentation for more information. o With MultiNet v4.4, the following keywords have been removed from the SSH1 server configuration file, SSHD_CONFIG, and are now defined using the command MULTINET CONFIGURE /SERVER. Port KeyRegenerationInterval STREAM Symbiont The MULTINET_STREAM_SYMBIONT has been modified to include detection and handling of "dead links", that is, a TCP/IP link that stops responding, but was not closed properly by the remote end. The default behavior is the same as the prior behavior. If you want the new dead link detection behavior, define the system logical as follows: $ define/sys MULTINET_STREAM_DEAD_LINK_TIMEOUT " [ [