Article ID: 824309 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to use a Citrix client to connect to a Citrix MetaFrame or a Citrix 1.8 installation that is hosted on a Windows 2000-based computer, you may experience a very long logon time (from 5 to 30 minutes) before the Citrix desktop appears.
This problem may occur if Windows 2000 Service Pack 4 (SP4) is installed on the server that you want to connect to, and all the following conditions are true:
Hotfix InformationA 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:
PrerequisitesWindows 2000 Service Pack 4.
Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.
File InformationThe English version of this hotfix 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 ---------------------------------------------------------- 17-Jul-2003 17:48 5.0.2195.6738 42,256 Basesrv.dll 17-Jan-2003 16:06 5.0.2195.6656 236,304 Cmd.exe 17-Jul-2003 17:48 5.0.2195.6762 222,992 Gdi32.dll 17-Jul-2003 17:48 5.0.2195.6741 711,440 Kernel32.dll 17-Jul-2003 17:48 5.0.2195.6751 333,072 Msgina.dll 08-Apr-2003 05:54 5.0.2195.6701 90,232 Rdpwd.sys 15-Jul-2003 22:08 5.0.2195.6776 4,858,368 Sp3res.dll 17-Jul-2003 17:48 5.0.2195.6785 380,176 User32.dll 17-Jul-2003 17:48 5.0.2195.6745 385,808 Userenv.dll 16-Jul-2003 23:32 5.0.2195.6784 1,628,784 Win32k.sys 17-Jul-2003 17:20 5.0.2195.6785 182,032 Winlogon.exe 17-Jul-2003 17:48 5.0.2195.6775 243,984 Winsrv.dll
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:
816915The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(http://support.microsoft.com/kb/816915/ )New Naming Schema for Microsoft Windows Hotfix Packages
Contact us for more help
Connect with Answer Desk for expert help.