Article ID: 321555 - View products that this article applies to.
This article was previously published under Q321555
This article has been archived. It is offered "as is" and will no longer be updated.
This article explains the three types of data encryption that are included with SNA Server and with Host Integration Server:
About data encryption
Server-to-server data encryptionEncryption of data is possible between two computers that are running SNA Server or Host Integration Server when you use the Distributed Link Service (DLS). You can use DLS encryption to provide secure communications across your network, the Internet, or any other wide area network (WAN).
When you use DLS, consider whether or not trust exists between the two Windows NT or Windows 2000 domains.
If trust does exist, note that for pass-through authentication to work, the branch (remote) SNA Server/Host Integration Server's link service must run under a domain user account that can be authenticated by the domain where the central (local) SNA Server or Host Integration Server computer resides. For example, the branch server's link service would be SNAREMx, that is, \\Central_Server\SnaDlcx.
If no Trust exists between the domains, the user account and password that the branch (remote) SNA Server/Host Integration Server's link service is running under must also exist in the accounts domain where the central (local) SNA Server or Host Integration Server computer resides for authentication to occur.
Also note that you cannot encrypt data by running the SNAREMx service under the local system account.
For more information about the Distributed Link Service, visit the following TechNet Web site:
Client sponsor connection data encryptionWhen an SNA or Host Integration Server client connects to a SNA Server or Host Integration Server computer over the sponsor connection, various messages are sent to the client. When you add the SecureSponsor registry parameter on the server that is running SNA Server or HIS, all sponsor connection data is encrypted.
For more information about how to use the SecureSponsor registry parameter, click the following article number to view the article in the Microsoft Knowledge Base:
159351For more information about the sponsor connection, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/159351/ )SecureSponsor disables SNA 3.0 Win 3.x Password Change feature
(http://support.microsoft.com/kb/160849/ )How the SNA Server client chooses a "sponsor" SNA server
(http://support.microsoft.com/kb/317805/ )Sponsor connection changes in Host Integration Server 2000
Client-to-server application data encryptionClient-to-server encryption prevents information from being sent in clear text between an SNA or Host Integration Server client and an SNA Server or Host Integration Server computer. You can enable client/server encryption on either a group or user-by-user basis.
Note By default, client/server encryption is enabled in Host Integration Server 2006 and in Host Integration Server 2004.
To configure users for client-server encryption, follow these steps:
Article ID: 321555 - Last Review: February 27, 2014 - Revision: 4.0