Microsoft KB Archive/262474

= Kerberos security with SNA Server and Host Integration Server =

Article ID: 262474

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 3.0 Service Pack 3
 * Microsoft SNA Server 3.0 Service Pack 4
 * 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 Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2004 Standard Edition

-



This article was previously published under Q262474



SUMMARY
SNA Server and Host Integration Server do not provide native Kerberos support, and therefore, do not leverage the use of the Kerberos authentication protocol, which is provided with Windows 2000.

SNA Server (and clients) and Host Integration Server (and end-user clients), continue to use Windows NT LanManager (NTLM) authentication for authentication protocol even if they are installed on Windows 2000 Server or Windows 2000 Professional).

SNA Server 4.0 Service Pack 3 (SP3) and later are supported on Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

251320 Installing SNA Server on Windows 2000



MORE INFORMATION
Although Windows 2000 uses Kerberos as the default authentication protocol, support for NTLM is still available for non-Kerberos clients for backwards compatibly.

For additional information about Kerberos, click the following article numbers to view the articles in the Microsoft Knowledge Base:

231789 Basic Overview of Kerberos Authentication in Windows 2000

231789 Local Logon Process for Windows 2000

Additional query words: HIS 2000

Keywords: kbinfo KB262474

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.