The information in this article applies to:
SYMPTOMSSNA Server notifies all SNA Server Windows NT clients of all invokable transaction programs (TPs) registered in the SNA dubdomain, even though the SNA Windows NT clients ignore these entries. This problem may cause no observable symptoms. However, it can cause excessive network traffic between SNA Windows NT clients and SNA Server computers if a large number of invokable TPs are registered within an SNA Server subdomain. This excessive traffic may lead to LAN connectivity problems between SNA Server Windows NT clients and the SNA Server computer. CAUSEEach SNA Server keeps track of all invokable transaction programs (TPs) registered on all servers and clients within the SNA Server subdomain. When SNA Server receives an FMH-5 attach message for a specific TP name, SNA Server routes the request to the appropriate server or client computer. Although SNA Server needs to advertise all registered invokable TPs to all other SNA Server computers in the subdomain, it also advertises these entries to all attached SNA Server Windows NT clients, which ignore this information. RESOLUTIONSNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:Q184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack SNA Server 4.0This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):S E R V P A C K STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 4.0. This problem was first corrected in SNA Server 3.0 Service Pack 4. Additional query words:
Keywords : kbfix4.00.sp1 prodsna snacpic snabaseservice snatp |
|
Last Reviewed: November 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |