Terminal Server Will Disconnect Users When Connected Remotely Through a Modem

This article was previously published under Q219540
This article has been archived. It is offered "as is" and will no longer be updated.
When you use a modem to connect remotely to a Microsoft Terminal Server computer, you may not stay connected after logging on to the Terminal Server session. The session cannot be established unless it is reset by an administrator.
This problem can occur if the connection is broken after it has been established through a modem, but before Terminal Server has properly transferred the connection internally.
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

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 Server 4.0, Terminal Server Edition Service Pack 4.

Article ID: 219540 - Last Review: 10/14/2013 19:44:39 - Revision: 2.2

Microsoft Windows NT Server 4.0, Terminal Server Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB219540
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)