Microsoft KB Archive/168096

From BetaArchive Wiki
Knowledge Base

Windows 95 SNA Server Client And Encryption Requirements

Article ID: 168096

Article Last Modified on 6/29/2004


  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 Service Pack 1
  • Microsoft SNA Server 4.0 Service Pack 2
  • Microsoft SNA Server 4.0 Service Pack 3
  • Microsoft SNA Server 4.0 Service Pack 4

This article was previously published under Q168096


The Microsoft Windows 95 SNA Server 4.0 Client requires one of the following to support the Data Encryption feature:

  • Client for Microsoft Networks
  • DCOM for Windows 95

If one of these components is not installed, and encryption is enabled for the user trying to access the SNA Server, the connection attempt will fail. The applets included with SNA Server will return errors similar to the following when this occurs.

5250 Applet:

There are no SNA Servers running in your domain.


3270 Applet:

ERROR - Reading SNA Server Configuration.


  • The Data Encryption feature requires that SNA Server clients are validated using the NTLM logon process. Third-party network redirectors such as Novell Netware Client 32 which do not provide the NTLM security interface will cause the user logon to fail when encryption is used.

    The Microsoft Network Client and DCOM for Windows 95 install the necessary NTLM security components to allow the user logon to succeed when encryption is used.

    DCOM for Windows 95 is a Windows 95 addon that provides support for distributed object computing. For more information on DCOM for Windows 95, please refer to the following Microsoft Web Page:
  • Encryption can be used over any of the client/server LAN transports supported by SNA Server.
  • The Windows 95 user does not need to logon to the Windows NT domain that the SNA Server belongs or or to any trusted domain in order to use encryption.
  • If the Client for Microsoft Networks is not installed, the Windows 95 SNA Server client needs to be configured so that the "Use Windows NT domain password" option is not selected under the Advanced tab in the client configuration. If this option is not selected, the Logon Domain has to be entered to specify which Windows NT Domain will be used to validate the user account. This also applies if the Client for Microsoft Networks is installed and a non-Named Pipe transport (in other words, TCP/IP or IPX/SPX) is selected for the SNA Server client.

Additional query words: snaencrypt

Keywords: KB168096