Err Msg: Logon Failure: User Not Granted the Requested Logon Type (223497)

SYMPTOMS

When you try to gain access to resources on a server that has the Microsoft LAN Manager Server EnableSecuritySignature parameter enabled, the following error message may be displayed:

Logon failure: the user has not been granted the requested logon type at this computer.

CAUSE

This error message occurs when a user on a computer running Windows NT 4.0 Service Pack 4 makes a remote connection to a computer running Windows NT 4.0 Service Pack 3 or Service Pack 4 and the LAN Manager Server EnableSecuritySignature parameter is set to 1. If the logged-on user has an account on the remote computer and the password differs between the two computers, the error message listed above occurs during any access request.

For additional information, please see the following article in the Microsoft Knowledge Base:

161372 How to Enable SMB Signing in Windows NT

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/ -or-
152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.