A Windows 2000 Terminal Server That Is Configured with Citrix Metaframe Software Can Become Slow and Unresponsive

This article has been archived. It is offered "as is" and will no longer be updated.
When you are running a Windows 2000 Terminal server that has Citrix Metaframe software installed, system performance may become slow or the computer may stop responding.
This problem may occur if you use the Callback feature and you configure this feature to use an asynchronous modem.

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File Information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version        Size     File name    --------------------------------------------------------   10-Feb-2003  11:57  5.0.2195.6654  125,712  Icaapi.dll    07-Oct-2002  05:29  5.0.2195.6609   93,456  Licmgr.exe    07-Apr-2003  10:09  5.0.2195.6701  330,512  Lserver.exe    10-Feb-2003  11:57  5.0.2195.6659   26,384  Mstlsapi.dll    29-Mar-2003  02:30  5.0.2195.6697  100,248  Rdpwsx.dll    28-May-2003  02:00  5.0.2195.6749  142,608  Termsrv.exe    26-Mar-2003  04:26  5.0.2195.6672   23,312  Tls236.dll    28-May-2003  02:01  5.0.2195.6701   39,184  Winsta.dll
To work around this problem, turn off the Callback feature:
  1. Click Start, point to Settings, and then click Network and Dial-up Connections.
  2. On the Advanced menu, click Dial-up Preferences.
  3. On the Callback tab, click No callback.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Article ID: 821225 - Last Review: 10/26/2013 18:47:08 - Revision: 2.5

Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Advanced Server

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