Microsoft KB Archive/104184: Difference between revisions
(importing KB archive) |
m (Text replacement - ">" to ">") |
||
| Line 51: | Line 51: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
After Telnet is started, if Terminal is closed before the TELNET | After Telnet is started, if Terminal is closed before the TELNET> prompt is displayed, you may receive an access violation error message. | ||
</div> | </div> | ||
| Line 58: | Line 58: | ||
== CAUSE == | == CAUSE == | ||
There is a timing window in the Telnet service that can cause the master thread to delete the client's critical section before the client thread terminates. This occurs if Terminal closes just before the master tries to write the TELNET | There is a timing window in the Telnet service that can cause the master thread to delete the client's critical section before the client thread terminates. This occurs if Terminal closes just before the master tries to write the TELNET> prompt. The master's write then fails, causing it to quit and delete the critical section. The client's read then fails, causing it to try to access the critical section during its termination processing. The client thread then access violates and the access violation error message is generated. | ||
</div> | </div> | ||
Latest revision as of 17:44, 20 July 2020
Article ID: 104184
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
This article was previously published under Q104184
SYMPTOMS
After Telnet is started, if Terminal is closed before the TELNET> prompt is displayed, you may receive an access violation error message.
CAUSE
There is a timing window in the Telnet service that can cause the master thread to delete the client's critical section before the client thread terminates. This occurs if Terminal closes just before the master tries to write the TELNET> prompt. The master's write then fails, causing it to quit and delete the critical section. The client's read then fails, causing it to try to access the critical section during its termination processing. The client thread then access violates and the access violation error message is generated.
STATUS
Microsoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. This problem was corrected in the latest U.S. Service Pack for Windows NT and Windows NT Advanced Server version 3.1. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Additional query words: prodnt
Keywords: kbnetwork KB104184
