This article was previously published under Q229012
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Terminal Server clients go into a "down" state and cannot be reset.
If a disconnected session has an active "Hard Error" dialog box that is generated by a DOS or 16-bit program, it cannot be reset. If a reset is attempted on the workstation, it stays in a "down" state until the computer is restarted.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
To work around this problem, you can disable dialog boxes from ever being displayed. This is done with a registry setting. For additional information, see the following article or articles in theMicrosoft Knowledge Base:
124873 Disabling System Hard Error Message Dialog Boxes
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Change the default value of 0 to 2.The following table defines the three possible values for ErrorMode:
Value Result ----- ---------------------------------------------------------------- 0 Errors are serialized and wait for a response. 1 If the error does not come from the system, then the system continues in normal operating mode. If the error comes from the system, then it is written to the system log; no user intervention is required and dialog boxes are not displayed. 2 The error is written to the system log; the dialog box is not displayed.
Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 5.