Can No Longer Access the Registry with Null Sessions

View products that this article applies to.

This article was previously published under Q143138

Expand all | Collapse all

SYMPTOMS

After you apply the security hotfix (Sec-fix) or Windows NT 4.0 Service Pack 3, which includes this hotfix, applications that use null sessions may no longer work properly.

For example, after you apply the security hotfix to a Windows NT computer running Cheyenne ARCServe 6.0, you may receive the following error message when you attempt to schedule a job (for example, local, remote, backup, and restore):

User doesn't have enough rights to do this
EC=5

Back to the top

CAUSE

The updated security modules for Windows NT no longer permit null sessions to access the Windows NT registry.

Back to the top

RESOLUTION

Perform the following steps to resolve this problem:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Run Registry Editor (Regedt32.exe).
Go to the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameter
Add "winreg" (without the quotation marks) to the NullSessionPipes entry.
Restart your computer.

Back to the top

MORE INFORMATION

For more information on the security hotfix (Sec-fix,) please see the following article(s) in the Microsoft Knowledge Base:

ARTICLE-ID: 143474 (http://support.microsoft.com/kb/143474/EN-US/ )
TITLE : Restricting Information Available to Anonymous Logon Users

ARTICLE-ID: 143475 (http://support.microsoft.com/kb/143475/EN-US/ )
TITLE : Windows NT System Key Permits Strong Encryption of the SAM

ARTICLE-ID: 161372 (http://support.microsoft.com/kb/161372/EN-US/ )
TITLE : How to Enable SMB Signing in Service Pack 3

This hotfix is also included with Windows NT 4.0 Service Pack 3.

Back to the top