This article was previously published under Q187936
This article has been archived. It is offered "as is" and will no longer be updated.
When running an application that calls LogonUser() from multiple threads,the second call to LogonUser may cause the application to hang. This occurswhen the user context under which the application is running does not havethe SE_TCB_NAME privilege.
NOTE: To set this privilege for a user, you can grant the user the advanceduser right to "Act as part of the operating system," in User Manager underUser Rights Policy.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.