This article was previously published under Q179983
This article has been archived. It is offered "as is" and will no longer be updated.
The problem occurs when multiple sessions access an image as a UNC name.When the first session to access the file logs off, the second session canno longer access the image.
Thread A impersonates a user and maps a file (typically, loads an image)using a UNC name. Another thread (thread B) impersonates a different userand maps the same file. Thread A logs off and thread A's session is loggedoff the server. Thread B cannot access the mapped file any longer.
Because of the way RDR and memory management work, thread B is accessingthe mapped file on thread A's user ID. When both threads first access theserver, two separate sessions are opened, creating two separate user IDs.However, when the session object is created to access the mapped file bythread B, and because it is the same file, it uses the same file objectthat was opened by thread A. The file object contains session informationthat the redirector uses to access the remote computer; therefore, thread Baccesses the file on thread A's session.
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.