Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. It takes four minutes for a computer that is running Windows Vista or Windows Server 2008 to open a Microsoft Office 2003 document from a network share

It takes four minutes for a computer that is running Windows Vista or Windows Server 2008 to open a Microsoft Office 2003 document from a network share

View products that this article applies to.

Symptoms

You have a computer that is running Windows Vista or Windows Server 2008. On this computer, you try to open a Microsoft Office 2003 document from a network share. In this case, it may take the computer four minutes to open the document.

This issue occurs only on the first attempt to open an Office 2003 document from the network share after you first communicate with the network share. Additional attempts to open Office 2003 documents from the network share succeed in a timely manner. Additionally, this issue occurs only when the following conditions are true:
  • The Office 2003 document is hosted on a network share on a remote computer.
  • You keep the computer connected to the network share for a long time before you open the Office 2003 document.
  • Server Message Block (SMB) signing is enabled on both the SMB server and the SMB client.

↑ Back to the top

Cause

The issue occurs since the SMB client does not set a correct flag to make a SMB connection when Kerberos ticket is expired and Kerberos re-authentication is required.

↑ Back to the top

Resolution

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 the problem described in this article. This hotfix might 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.

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, contact 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 website:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

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:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use this hotfix, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The 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 Vista and Windows Server 2008 file information notes
Important 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.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    0.
    20xxx    		Windows VistaRTMLDR
    6.0.600
    1.
    22xxx    		Windows Vista and Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx    		Windows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Vista andWindows Server 2008
File nameFile versionFile sizeDateTimePlatform
Mrxsmb20.sys6.0.6001.2272479,36005-Jul-201013:12x86
Mrxsmb20.sys6.0.6002.2243980,38405-Jul-201013:45x86
Mrxsmb.sys6.0.6001.22724106,49605-Jul-201013:12x86
Mrxsmb.sys6.0.6002.22439106,49605-Jul-201013:45x86
For all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Mrxsmb20.sys6.0.6001.22724106,49605-Jul-201013:32x64
Mrxsmb20.sys6.0.6002.22439107,52005-Jul-201013:55x64
Mrxsmb.sys6.0.6001.22724135,16805-Jul-201013:32x64
Mrxsmb.sys6.0.6002.22439135,68005-Jul-201013:55x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Mrxsmb20.sys6.0.6001.22724262,65605-Jul-201013:15IA-64
Mrxsmb20.sys6.0.6002.22439265,72805-Jul-201013:30IA-64
Mrxsmb.sys6.0.6001.22724320,00005-Jul-201013:15IA-64
Mrxsmb.sys6.0.6002.22439320,51205-Jul-201013:30IA-64

↑ Back to the top

Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To work around this issue, use registry keys to disable SMB signing. To do this, follow these steps:
  1. Click Start, type regedit in the Search programs and files box, and then press ENTER.
  2. On a server, locate and then click the following registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters
  3. On a client computer, locate and then click the following registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters
  4. Disable these two registry keys. To do this, follow these steps:
    1. Right-click Enablesecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK .
    2. Right-click Requiresecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK.


↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

Steps to reproduce this issue

  1. On a computer that is running Windows Vista, connect to a network share on a file server that also works as a domain controller.
  2. Open a Microsoft Office Excel 2003 file from the file server.
  3. Close the Excel 2003 file, and then lock the computer.
  4. Keep the computer running overnight.
  5. Log on to the computer the next morning.
  6. Try to open any Office 2003 file from the file server.
In this case, you experience a four-minute delay before the Office 2003 file opens.

For more information about how to use SMB packet signing, visit the following Microsoft website:
Using SMB Packet Signing

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
982860 A computer that is running Windows 7 or Windows Server 2008 R2 takes four minutes to open a Microsoft Office 2003 document from a network share

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size3,577
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameX86_2f73ee046a1e2ba63be2ae28df8e7e50_31bf3856ad364e35_6.0.6001.22724_none_90bfbe3d4c096df7.manifest
File versionNot applicable
File size698
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameX86_577c4c9b650d7766607f0330b51ab348_31bf3856ad364e35_6.0.6002.22439_none_8170c5f3cdc149dd.manifest
File versionNot applicable
File size698
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameX86_7061508b9110cb9db9907887ed902b74_31bf3856ad364e35_6.0.6001.22724_none_e918ff5b36538912.manifest
File versionNot applicable
File size701
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameX86_ba81b36e763c61f23bba6ade8616be7b_31bf3856ad364e35_6.0.6002.22439_none_8954be16ef8d97e6.manifest
File versionNot applicable
File size701
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameX86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6001.22724_none_8b52ff1aa2f00ce8.manifest
File versionNot applicable
File size6,960
Date (UTC)05-Jul-2010
Time (UTC)15:30
PlatformNot applicable
File nameX86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22439_none_8d33a288a019fcb0.manifest
File versionNot applicable
File size6,960
Date (UTC)05-Jul-2010
Time (UTC)18:03
PlatformNot applicable
File nameX86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6001.22724_none_800976b46a479b15.manifest
File versionNot applicable
File size8,844
Date (UTC)05-Jul-2010
Time (UTC)15:21
PlatformNot applicable
File nameX86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6002.22439_none_81ea1a2267718add.manifest
File versionNot applicable
File size8,844
Date (UTC)05-Jul-2010
Time (UTC)17:58
PlatformNot applicable


Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_2e78f215fe42e3d59421e4e8caf989df_31bf3856ad364e35_6.0.6001.22724_none_93767e4a3d00d6b3.manifest
File versionNot applicable
File size705
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameAmd64_89d2439171cc33eb7429ccd20a47295b_31bf3856ad364e35_6.0.6002.22439_none_2affd4b9ce9e8a10.manifest
File versionNot applicable
File size705
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameAmd64_c350be507e1204796f40cbb956a6fbd2_31bf3856ad364e35_6.0.6001.22724_none_97206592b7c60613.manifest
File versionNot applicable
File size702
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameAmd64_f1345970adb241bbccb0ae218cbd09aa_31bf3856ad364e35_6.0.6002.22439_none_2ba64c12b3c8c3cf.manifest
File versionNot applicable
File size702
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameAmd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6001.22724_none_e7719a9e5b4d7e1e.manifest
File versionNot applicable
File size6,972
Date (UTC)05-Jul-2010
Time (UTC)15:45
PlatformNot applicable
File nameAmd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22439_none_e9523e0c58776de6.manifest
File versionNot applicable
File size6,972
Date (UTC)05-Jul-2010
Time (UTC)18:22
PlatformNot applicable
File nameAmd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6001.22724_none_dc28123822a50c4b.manifest
File versionNot applicable
File size9,112
Date (UTC)05-Jul-2010
Time (UTC)15:39
PlatformNot applicable
File nameAmd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6002.22439_none_de08b5a61fcefc13.manifest
File versionNot applicable
File size9,112
Date (UTC)05-Jul-2010
Time (UTC)18:16
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,605
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable


Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_1721222cd55504f2482c23e746b10e00_31bf3856ad364e35_6.0.6001.22724_none_df1704397c73cc3e.manifest
File versionNot applicable
File size703
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameIa64_4a9a0630936212d03299f9e176095d76_31bf3856ad364e35_6.0.6001.22724_none_247df8e09524e994.manifest
File versionNot applicable
File size700
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameIa64_53248586b658b332b0a306b5584c4eda_31bf3856ad364e35_6.0.6002.22439_none_586f1af50e52bf72.manifest
File versionNot applicable
File size703
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameIa64_a0d9e4cfbf11d6ca884ff103e7e1fcf4_31bf3856ad364e35_6.0.6002.22439_none_10a24417caee353c.manifest
File versionNot applicable
File size700
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable
File nameIa64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6001.22724_none_8b54a310a2ee15e4.manifest
File versionNot applicable
File size6,966
Date (UTC)05-Jul-2010
Time (UTC)15:15
PlatformNot applicable
File nameIa64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22439_none_8d35467ea01805ac.manifest
File versionNot applicable
File size6,966
Date (UTC)05-Jul-2010
Time (UTC)16:14
PlatformNot applicable
File nameIa64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6001.22724_none_800b1aaa6a45a411.manifest
File versionNot applicable
File size9,103
Date (UTC)05-Jul-2010
Time (UTC)15:11
PlatformNot applicable
File nameIa64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6002.22439_none_81ebbe18676f93d9.manifest
File versionNot applicable
File size9,103
Date (UTC)05-Jul-2010
Time (UTC)16:07
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,758
Date (UTC)06-Jul-2010
Time (UTC)05:49
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2272153
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 232