NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SNADS Unlimited-User Upgrade v1.0 B to v1.0 C DOCUMENT ID: TID200026 DOCUMENT REVISION: A DATE: 06DEC93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: NGM176.EXE NOVELL PRODUCT and VERSION: SNADS for NetWare Global MHS ABSTRACT: This patch program will upgrade your NGMSNADS unlimited-user version 1.0 revB to version 1.0 revC. This patch program replaces the SNADSL2 and SNADSL3 patches and will upgrade these patched versions of NGMSNADS v1.0 revC to the latest revC level. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ADDITIONAL CONFIGURATION Before installing this patch, you must be running NetWare Global MHS v2.00b or a subsequent version. If you have NetWare for Global Messaging v1.0 or NetWare Global MHS v2.00, you can obtain the patch for v2.00b from any of the following sources: * NetWire * by sending a message to library@novell with subject: guide * Novell Technical Support SYMPTOM SNADS Update needed TROUBLESHOOTING Troubleshooting Hints ===================== For detailed troubleshooting instructions, refer to Chapter 8 of the NetWare Global Messaging SNADS Protocol Module Administrator's Guide. Following are suggestions for troubleshooting common problems. Problem: Messages from SNADS are remaining in the NGM queue, with the following workgroup name: -unauthorized-.workgroup Action: This error occurs if you are using a limited-user version of the SNADS protocol module. The NetWare Global MHS recipient is not defined as an authorized user. Add the user to the list of authorized users, following the instructions in Chapter 6 of the guide. Problem: The SNADS node is rejecting messages received from the SNADS protocol module. Action: Check the maximum number of recipients for which your SNADS node is configured. If it is less than 256, add the following parameter to the [NGMSNADS] section of your server's NGM.CFG file: Maximum-Recipients= where is the maximum number of recipients your SNADS node will accept. For more information about NGM.CFG, refer to Appendix B of the guide. Problem: Global MHS users are receiving non-delivery notifications that contain no explanation of the reason for non-delivery. Action: a. If you are using a limited-user version of SNADS for Global MHS, make sure the sender has been authorized to send messages to SNADS. Refer to chapter 6 of the "NetWare Global Messaging SNADS Protocol Module Administrator's Guide" for detailed instructions. b. Check for communication problems. This error occurs if there is an unrecoverable communication error while SNADS for Global MHS is transmitting a message to the SNADS node. Problem: Messages from SNADS are arriving at their destination in binary format. The destination server does not connect to SNADS directly, but through an intermediate server. Action: a. (Recommended solution) In the SNADS directory, do not define servers that connect to SNADS indirectly. Instead, define their DGNs as belonging to the server that does connect directly. For example, Server1 connects to SNADS directly; Server2 communicates with SNADS through Server1. Server2 has two workgroups, Personnel (SNADS alias=PERSONNE) and Finance (SNADS alias=FINANCE). In the SNADS directory, PERSONNE and FINANCE are defined as DGNs at Server1. b. If you prefer to define indirectly-connected servers in the SNADS directory, ensure that the SNADS alias for the directly-connecting server contains the aliases for all servers to which it routes messages received from SNADS. For example, if Server2 (RGN=ACME, REN=SERVER2) is defined in the SNADS directory, you must define the following SNADS alias for Server1 (RGN=ACME, REN=SERVER1): ACME.SERVER1,ACME.SERVER2 Problem: Directory information received from DISOSS is not being integrated into the Global MHS database. Action: Ensure that your Global MHS server subscribes to the DISOSS workgroups. For more information, refer to Chapter 7 of the guide. General Information =================== This section provides additional information about the SNADS protocol module. * If a session terminates while the SNADS protocol module is delivering a message to SNADS, the SNADS protocol module will resend the message during the next session. If the message was delivered successfully before the termination occurred, two copies of the message might be delivered to the SNADS recipient. * When a DISOSS user sends a message to a NetWare Global MHS distribution list, DISOSS receives a DIA status (delivery report) from each of the list members. Since the list member names do not match the original recipient name (the distribution list), the message status is not updated. For example, a DISOSS user sends a message to a NetWare Global MHS list called "Managers." NetWare Global MHS distributes the message to John Smith and Mary Adams, the list members. DISOSS receives DIA statuses from John and Mary, but it does not receive one from "Managers," the original recipient. Therefore, it does not update the message status. * SMF short names can only include letters, numbers, and the following special characters: #, $, and -. To ensure compatibility between SNADS and NetWare Global MHS, do not use unsupported characters (such as spaces) in SNADS names. * If you are using DISOSS Directory Synchronization, workgroups in your organization must not include both DISOSS and NetWare Global MHS users. * SNADS for Global MHS cannot detect the Keyword document translation program (DOCXLT) when it is auto-loaded by NGM. If document translations are not being invoked, unload DOCXLT and reload it manually. * The Keyword document translation program (DOCXLT) has an auto-detection feature that allows it to determine a document type. However, this feature might identify a binary file as type TEXT, and attempt to convert it. This results in corruption of the file. SOLUTION Apply NGM176.EXE Self-Extracting File Name: NGM176.EXE Revision: A Files Included Size Date Time \ NGM176.TXT (This File) RELNOTE.TXT 18628 10-18-93 9:52a PATCH.EXE 45928 07-01-93 2:00a PATCH.RTP 129654 10-18-93 10:38a Installation Instructions: TO APPLY THIS PATCH: =================== 1) Delete PATCH.* from the NGM\BIN directory if you have applied previous NGM patches. 2) Copy the files PATCH.EXE and PATCH.RTP to your NGM\BIN subdirectory. 3) Change directories to your NGM\BIN directory. 4) Make a backup copy of the following NGMSNADS 1.00b files: NGMSNADS.NLM (dated 01-08-93 ; 2697 bytes in size) SNADSCON.NLM (dated 01-11-93 ; 133940 bytes in size) SNADSRUN.NLM (dated 02-09-93 ; 274998 bytes in size) SNADUINS.NLM (dated 01-07-93 ; 2539 bytes in size) SNADSCON.HLP (dated 01-11-93 ; 3943 bytes in size) If you have previously applied the SNADSU2 patch, your current NGMSNADS files will have the following file statistics: NGMSNADS NLM 2722 08-11-93 4:06p SNADSCON NLM 156337 08-11-93 4:00p SNADSRUN NLM 288482 09-08-93 5:16p SNADUINS NLM 3005 08-03-93 4:04p SNADSCON HLP 6686 06-29-93 11:24a If you have previously applied the SNADSU3 patch, your current NGMSNADS files will have the following file statistics: NGMSNADS NLM 2722 08-11-93 4:06p SNADSCON NLM 156337 08-11-93 4:00p SNADSRUN NLM 288615 09-22-93 5:55p SNADUINS NLM 3005 08-03-93 4:04p SNADSCON HLP 6686 06-29-93 11:24a 5) Run the program PATCH.EXE (with no parameters). 6) If the patch succeeds, delete PATCH.EXE and PATCH.RTP. The resulting NGMSNADS files will have the following file statistics: NGMSNADS NLM 2722 08-11-93 4:06p SNADSCON NLM 156337 08-11-93 4:00p SNADSRUN NLM 288727 10-14-93 12:27p SNADUINS NLM 3005 08-03-93 4:04p SNADSCON HLP 6686 06-29-93 11:24a 7) If the patch fails, restore the files backed up in Step 4 and contact Novell Technical Support for additional help. Solution Specifics: Features ======== The SNADS protocol module provides the following features: * Transfers messages between NetWare Global MHS and SNADS endpoints using an existing SNA network. * Provides support for the SNA communications protocols. * Supports connections via direct token ring, ethernet, or SDLC to an SNA wide area network. (Note that the connection parameters for ethernet are the same as the connection parameters for token ring). * Supports one or more LU6.2 sessions and up to two PU2.0 or 2.1 connections. * Supports automatic directory synchronization between DISOSS and NetWare Global MHS. * Supports SMF extended addresses. * Allows you to choose whether header information (such as To:, From:, Subject:, cc:, and Date:) will be included in messages sent to SNADS. * Allows you to choose whether original messages will be included in messages replied to by SNADS users. Extended Address Support ======================== A new feature in SNADS for NetWare Global MHS allows SNADS users to include SMF extended addresses in messages sent to NetWare Global MHS. Because SNADS users can now include address extensions in their messages, the Global MHS server administrator no longer needs to define users with extended addresses in the SNADS Auto-Registration Table. Some environments, such as fax and X.400, require special address information. To support these environments, the SMF protocol contains an extended address field. For example, to send a message to Sharon Carstairs through a fax gateway, a NetWare Global MHS user would address the message to Sharon Carstairs@FaxGate {Fax:1-555-1234/Sharon Carstairs}. However, SNADS does not support extended addresses. To enable SNADS users to send to these environments, the SNADS protocol module allows SNADS users to include extended addresses in their messages. SNADS users can enter extended addresses in one (and only one) of the following three locations: at the beginning of the message; in the subject; or at the beginning of the document. The SNADS protocol module scans these three locations in the order in which they are listed. If it finds an extended address in one of these locations, it will ignore any extended addresses in the others. An extended address definition begins with two open angle brackets (<<) and ends with two closed angle brackets (>>). Between the beginning and ending markers are one or more address extensions, separated by one or more spaces. Thus, the syntax of the extended address definition is as follows: <> Each extension definition has one of the following formats: dgn.den={extended address} dgn.den=(extended address) dgn.den="extended address" where dgn.den is a recipient specified in the address (TO and CC) fields. The extended address can be enclosed in braces, parentheses, or double quotation marks. If a message has only one recipient, the dgn.den= can be omitted from the extended address definition. For example, Pam Pratt is a SNADS user who wants to send a message to Sharon Carstairs. Messages for Sharon are routed through NetWare Global MHS to a fax gateway. Pam creates the following message: TO: FAXGATE.SCARSTAI SUBJECT: <<{Fax:1-555-1234/Sharon Carstairs}>> Because the message is addressed to only one user, Pam does not include the dgn.den=. Consider a second example. Pam Pratt wants to send a message to Sharon Carstairs, Jack Smith, a Global MHS user, and Donna White, an X.400 user. Messages for Donna are routed through NetWare Global MHS to an X.400 Gateway. Pam creates the following message: TO: FAXGATE.SCARSTAI NEWYORK.JSMITH X400GATE.DWHITE SUBJECT: Monthly Update << FAXGATE.SCARSTAI={Fax:1-555-1234/Sharon Carstairs} X400GATE.DWHITE={X400:C=US;A=Publicmail;P=ABC;O=ABC;G=Donna;S=Wh ite} >> Sharon and Donna: The update will be delayed one day. We will be sending it tomorrow. Because the message is addressed to more than one user, Pam must include the dgn.den=. SNADS Protocol Module Training ============================== Self-paced study course #1760, titled Administering SNADS for NetWare Global MHS, is available. NetWare Global MHS training course #750 provides comprehensive instruction in installation, configuration, and administration of the NetWare Global MHS software. For more information about either of these training courses, call (800) 233-3382 or (801) 429-5508, or contact your local Novell authorized education center. Contacting Novell Messaging Technical Support Should you need technical support for NetWare Global MHS, contact your Novell reseller, or Novell at (800) NETWARE or (801) 429-5588. **************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to this software patch, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of this patch is forbidden without the express written consent of Novell, Inc. Novell reserves the right to discontinue distribution of this software patch. Novell will not be responsible for any data loss that may result from implementing this patch. Novell strongly recommends a backup be made before any patch is applied. Technical support for this patch is provided at the discretion of Novell. **************************************************** �