You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
76 lines
5.4 KiB
76 lines
5.4 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
|
|
<HTML DIR="LTR">
|
|
<HEAD>
|
|
<TITLE>Compatibility Details</TITLE>
|
|
<META HTTP-EQUIV="Content-Type" CONTENT="text-html;charset=Windows-1252">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#ffffff">
|
|
<FONT FACE="verdana" SIZE="2">
|
|
<P>Windows 95 and Windows NT 4.0 interoperability issues.
|
|
</P>
|
|
<P> </P>
|
|
<P>SUMMARY
|
|
</P>
|
|
<P>Windows Server 2003 Domain Controllers implement default security settings
|
|
that help prevent Domain Controller communications from being hijacked or
|
|
otherwise tampered with. Certain downlevel machines are not capable of meeting
|
|
these security requirements and thus cannot communicate with Windows Server 2003 Domain
|
|
Controllers without administrative intervention.
|
|
</P>
|
|
<P>Affected machines include Windows for Workgroups, Windows 95 machines that do not have the DS client pack installed, Windows NT 4.0 machines prior to Service Pack 4, and devices, including Pocket PC 2002 and previous versions, based on the Windows CE .NET version 4.1 or earlier.</P>
|
|
<P> </P>
|
|
<P>SMB SIGNING</P>
|
|
<P>By default, Windows Server 2003 Domain Controllers require that all clients digitally sign SMB-based communications. The SMB protocol is used to provide file sharing, print sharing, various remote administration functions, and logon authentication for some downlevel clients. Windows for Workgroups, Windows 95 machines without the DS Client Pack, Windows NT 4.0 machines prior to Service Pack 3, and devices, including Pocket PC 2002 and previous versions, based on the Windows CE .NET version 4.1 or earlier are not capable of performing SMB signing and therefore cannot connect to Windows Server 2003 Domain Controllers by default. If such clients cannot be upgraded to a current operating system or upgraded to meet the minimum requirements described above, then the SMB signing requirement can be removed by disabling the following security policy in the Default Domain Controller GPO on the domain controllers OU:
|
|
</P>
|
|
<P>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft Network Server: Digitally sign communications (always)</P>
|
|
<P>Detailed instructions on how to modify this setting are provided below.</P>
|
|
<P>Warning: Disabling this security setting exposes all of your Domain Controller communications to "man in the middle" types of attacks. Therefore it is highly recommended that you upgrade your clients rather than disabling this security setting. The DS Client Pack, necessary for Windows 95 clients to perform SMB signing, can be obtained from the \clients\win9x sub-directory of the Windows 2000 Server CD.</P>
|
|
<P> </P>
|
|
<P>SECURE CHANNEL SIGNING</P>
|
|
<P>By default, Windows Server 2003 Domain Controllers require that all secure channel communications be either signed or encrypted. Secure channels are used by Windows NT-based machines for communications between domain members and domain controllers as well as between domain controllers that have a trust relationship. Windows NT 4.0 machines prior to Service Pack 4 are not capable of signing or encrypting secure channel communications. If Windows NT 4.0 machines prior to SP4 must join this domain, or this domain must trust other domains that contain pre-SP4 Domain Controllers, then the secure channel signing requirement can be removed by disabling the following security policy in the Default Domain Controller GPO:</P>
|
|
<P>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Domain Member: Digitally encrypt or sign secure channel data (always)</P>
|
|
<P>Detailed instructions on how to modify this setting are provided below.</P>
|
|
<P>Warning: Disabling this security setting exposes secure channel communications to "man in the middle" types of attacks. Therefore it is highly recommended that you upgrade your Windows NT 4.0 machines rather than disabling this security setting.</P>
|
|
<P> </P>
|
|
<P>MODIFYING THE DEFAULT DOMAIN CONTROLLER GPO</P>
|
|
<P>To ensure all domain controllers are enforcing the same SMB and secure channel
|
|
signing requirements, define the corresponding security settings in the Default
|
|
Domain Controller GPO as follows:</P>
|
|
<OL>
|
|
<LI>
|
|
Log on to a machine that has the Active Directory Users and Computers Snap-in
|
|
installed.
|
|
</LI>
|
|
<LI>
|
|
Start --> Run --> DSA.MSC
|
|
</LI>
|
|
<LI>
|
|
Expand the Domain that contains your Windows Server 2003 Domain Controllers.
|
|
</LI>
|
|
<LI>
|
|
Right-click on the Domain Controllers OU, and then click Properties.
|
|
</LI>
|
|
<LI>
|
|
Click the Group Policy tab, select the "Default Domain Controller Policy", and
|
|
then click Edit.
|
|
</LI>
|
|
<LI>
|
|
Expand Computer Configuration, Windows Settings, Security Settings, Local
|
|
Policies, Security Options
|
|
</LI>
|
|
<LI>
|
|
In the result pane, double click the security option you want to modify. For
|
|
example, Microsoft Network Server: Digitally sign communications (always) or
|
|
Domain Member: Digitally encrypt or sign secure channel data (always).
|
|
</LI>
|
|
<LI>
|
|
Check the "Define this policy setting" box.
|
|
</LI>
|
|
<LI>
|
|
Disable or Enable the security setting as desired, and then select OK.
|
|
</LI>
|
|
</OL>
|
|
|
|
</FONT>
|
|
</BODY>
|
|
</HTML>
|