| | How to use the RestrictAnonymous registry value in Windows 2000 |
| (246261) - This article describes how administrators can use the RestrictAnonymous registry value on a Windows 2000-based computer to restrict access over anonymous connections. http://support.microsoft.com/kb/246261 |
| | The "RestrictAnonymous" Registry Value May Break the Trust to a ... |
| (296405) - With User Manager, when you attempt to add users or global groups from a trusted Windows 2000 domain (on a Windows NT 4.0 domain controller) to a local group in the Windows NT 4.0 ... http://support.microsoft.com/kb/296405 |
| | RestrictAnonymous Access Enabled Lets Anonymous Connections Obtain the ... |
| (129457) - Windows NT 4.0 with Service Pack 3 (SP3) installed provides the capability to restrict anonymous users from obtaining system information. For more information, please see the ... http://support.microsoft.com/kb/129457 |
| | The RestrictAnonymous value breaks the trust in a mixed-domain ... |
| (296403) - When you try to add users or global groups from a trusted Windows NT 4.0 domain with Active Directory Users and Computers on a Windows 2000 domain controller, the following error ... http://support.microsoft.com/kb/296403 |
| | Link Target Servers in DFS Referral Responses Are Sometimes Sorted in ... |
| (824730) - A domain controller that is successfully contacted has the RestrictAnonymous registry value set to 2. Note You can resolve this problem by lowering the RestrictAnonymous registry ... http://support.microsoft.com/kb/824730 |
| | Could Not Find Domain Controller When Establishing a Trust |
| (178640) - Set the RestrictAnonymous value to 0 in the registry, or remove the value to establish the trust. Open Registry Editor. Locate the following key in the registry: http://support.microsoft.com/kb/178640 |
| | How to Troubleshoot Inter-Forest Password Migration with ADMTv2 |
| (322981) - The RestrictAnonymous value on the target domain controller should be set to 0 during the migration. Read permissions on the Pre-Windows 2000 Compatible Access group should be ... http://support.microsoft.com/kb/322981 |
| | Restricting information available to anonymous logon users |
| (143474) - The Server service that provides remote file access to share resources will also use the LSA registry value, RestrictAnonymous, to control whether anonymous connections ... http://support.microsoft.com/kb/143474 |
| | The effects of removing null sessions from the Microsoft Windows 2000 ... |
| (890161) - The RestrictAnonymous registry value was introduced in Microsoft Windows NT 4.0 Service Pack 3 (SP3) and is now included with Windows 2000. The RestrictAnonymous registry value is ... http://support.microsoft.com/kb/890161 |
| | Trust between a Windows NT domain and an Active Directory domain ... |
| (889030) - The RestrictAnonymous GPO: Windows NT registry location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rdr\Parameters; Windows 2000 and Windows Server 2003 ... http://support.microsoft.com/kb/889030 |
| | "You do not have permission to change your password" error message ... |
| (328817) - This scenario occurs when updates to Group Policy change the RestrictAnonymous setting to 2. In the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry subkey ... http://support.microsoft.com/kb/328817 |
| | Users Cannot Change Password When Logging On |
| (198941) - To work around this problem, remove the RestrictAnonymous entry or set the value to 0, and then restart the PDC. This workaround will resolve both scenarios above. http://support.microsoft.com/kb/198941/) |
| | "System Cannot Log You On to This Domain" Error Message When You Try ... |
| (810497) - HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LMcompatibilitylevel HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\RestrictAnonymous http://support.microsoft.com/kb/810497 |
| | Troubleshooting Server Message Block inbound connection limit in ... |
| (328459) - Note In Windows XP, the RestrictAnonymous subkey can have a value of 0 or 1. A value of 1 restricts null session connections on Windows XP-based clients. http://support.microsoft.com/kb/328459 |
| | XADM: Clients Cannot Browse the Global Address List After You Apply ... |
| (309622) - This issue can occur if you use the Q299687 Windows 2000 security hotfix and you set the RestrictAnonymous registry key to a value of 0x2. http://support.microsoft.com/kb/309622 |
| | Add Workstation Fails with RestrictAnonymous |
| (192126) - An error occurs when the Remoteboot service attempts to update the Access Control List (ACL) on new workstations in the Rpl files\Workstations folder. The service appears to be ... http://support.microsoft.com/kb/192126 |
| | Outlook Clients Cannot View Global Address List After You Install ... |
| (318866) - This behavior may occur if the RestrictAnonymous registry value on the Global Catalog servers is set to 2. For additional information about the RestrictAnonymous registry value ... http://support.microsoft.com/kb/318866 |
| | Security issues with LDAP NULL base connections |
| (837964) - Note Microsoft does not support using RestrictAnonymous with a value of 2. This setting may cause serious problems, especially in mixed environments with earlier-version clients ... http://support.microsoft.com/kb/837964 |
| | The Net Logon Service of a Windows NT 4.0 BDC Does Not Function in a ... |
| (293127) - To change the value of RestrictAnonymous: Start Registry Editor (Regedt32.exe). Locate the RestrictAnonymous value under the following key in the registry: http://support.microsoft.com/kb/293127/) |
| | Error message when you try to access a Windows XP-based network ... |
| (913628) - For more information about the restrictanonymous registry entry, click the following article number to view the article in the Microsoft Knowledge Base: http://support.microsoft.com/kb/913628 |
|