Select the product you need help with
Applications or services that use the NFS redirector may crash when a Linux-based client or a UNIX-based client disconnects from a Windows Server 2003 or Windows Server 2008 terminal server without logging offArticle ID: 959200 - View products that this article applies to. On This PageSYMPTOMSConsider the following scenario:
When this problem occurs, you have to restart the terminal server to restore the connection to the Linux-based computer or to the UNIX-based computer. CAUSEThis problem occurs because a deadlock occurs in NFS after the client connection to the terminal server is reset. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must be running Windows Server 2003 Service Pack 2 or Windows Server 2008 Service Pack 2 on the computer.For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base: 889100
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
968849
(http://support.microsoft.com/kb/968849/
)
How to obtain the latest service pack for Windows Server 2008
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows Server 2003 file information notes
Windows Server 2003 with Service Pack 2, x86-based versionsCollapse this table
Windows Server 2003 with Service Pack 2, x64-based versionsCollapse this table
Windows Server 2003 with Service Pack 2, Itanium-based versionsCollapse this table
Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
For all supported x86-based versions of Windows Server 2008Collapse this table
For all supported x64-based versions of Windows Server 2008Collapse this table
For all supported IA-64-based versions of Windows Server 2008Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONWhen the MRxCreateVNetRoot routine returns the STATUS_CONNECTION_RESET error code, the client connection to the terminal server is reset. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesMORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file informationAdditional file information for Windows Server 2008Additional files for all supported x86-based versions of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008Collapse this table
Additional files for all supported IA-64-based versions of Windows Server 2008Collapse this table
PropertiesArticle ID: 959200 - Last Review: October 8, 2011 - Revision: 3.0 APPLIES TO
|



Back to the top








