Problems with the Windows NT Client Configuration Tool

Last reviewed: March 18, 1998
Article ID: Q182531
The information in this article applies to:
  • Microsoft SNA Server version 4.0

SYMPTOMS

The following four problems occur with the Client Configuration tool in the SNA Server Windows NT client, version 4.0:

  • When you select IPX as the transport with the SNA Server Windows NT client, the following choices are available on the Client Mode tab during the client's initial installation:

        - Client locates servers in an SNA Server subdomain
        - Client locates servers by name
    

    However, if you select IPX as the transport in the SNA Server Windows NT Client Configuration tool (Ntconfig.exe) after installation, the only option under Client Mode is:

          Client locates servers in an SNA Server subdomain
    
  • When you click OK to exit the SNA Server Windows NT client Configuration tool (Ntconfig.exe), Ntconfig.exe indicates that SNABASE needs to be restarted even if no changes have been made to the configuration.
  • On the Client Mode tab in Ntconfig.exe, if you select "Client locates servers in an SNA subdomain" and you do not enter a Subdomain name, the configuration is changed to "Client locates server by name" with an empty Server(s) list.
  • If Snaver.exe is run against Ntconfig.exe, the SNA Server Version Info dialog box displays the following:

            NTCONFIG.EXE
            Version 4.0.0.500
            NTCONFIG Version 1.0
    
    

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : snasetup snawinnt kbbug4.00
Version           : WINDOWS:4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.