Back Level SNA Manager May Save Com.cfg Incorrectly (186711)


The information in this article applies to:

  • Microsoft SNA Server 3.0
  • Microsoft SNA Server 3.0 SP1
  • Microsoft SNA Server 3.0 SP2
  • Microsoft SNA Server 3.0 SP3
This article was previously published under Q186711

SUMMARY

Several new features have been added to SNA Server that have resulted in changes to the SNA Server's configuration file (Com.cfg). One such addition is multi-SAP support that allows the selection of the Local and Remote SAP from the connection. Back-level clients are not aware of this change and may overwrite the information stored in the Com.cfg file that represents this information. Connection problems may not be evident until the server is restarted or the SNA Server service is cycled.

MORE INFORMATION

When you use SNA Manager to administer an SNA Server subdomain, care should be taken to ensure all SNA Servers and SNA WinNT clients that make and save changes to the configuration file (Com.cfg), are running a service pack at least equal to the service pack level installed on the Primary SNA Server of that subdomain.
Modification Type:MajorLast Reviewed:6/24/2004
Keywords:kbinfo KB186711
©2004 Microsoft Corporation. All rights reserved.