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. On a computer that is running Windows Vista or Windows Server 2008, iSCSI Initiator may be unable to communicate with the iSCSI target for several minutes after an iSCSI Protocol Data Unit (PDU) is rejected

On a computer that is running Windows Vista or Windows Server 2008, iSCSI Initiator may be unable to communicate with the iSCSI target for several minutes after an iSCSI Protocol Data Unit (PDU) is rejected

View products that this article applies to.

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You use Microsoft iSCSI Initiator to connect to an iSCSI target from a computer that is running Windows Vista or Windows Server 2008.
  • An iSCSI Protocol Data Unit (PDU) is rejected by the target for one of the reasons that are outlined in section 10.17.1 of iSCSI Specification Request for Comment (RFC) 3720.
In this scenario, iSCSI Initiator should resend the PDU that was rejected by the iSCSI target. However, iSCSI Initiator may be unable to communicate with the iSCSI target for several minutes.

Specifically, iSCSI Initiator cannot communicate with the target for a period of five times the Disk Timeout value that is specified in the following registry entry:
Subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk
Entry: TimeoutValue
Type: REG_DWORD
Value: The Disk Timeout Value in seconds
After a period of five times the Disk Timeout Value elapses, iSCSI Initiator performs session recovery, and then the iSCSI session is dropped and reestablished. Eventually, iSCSI Initiator may be able to communicate with the iSCSI target again.

↑ Back to the top

Cause

This problem may occur because of a defect in how iSCSI Initiator determines how many times it has re-sent a rejected PDU. This defect makes the iSCSI target unresponsive. Therefore, iSCSI Initiator performs LUN resets in order to communicate with the iSCSI target. It does this instead of immediately retrying the rejected PDU.

↑ Back to the top

Resolution

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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 Web site:
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 on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductMilestoneService branch
    6.0.6000.16xxxWindows VistaRTMGDR
    6.0.6000.20xxxWindows VistaRTMLDR
    6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR
    6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDR
  • Service Pack 1 is integrated into Windows Server 2008.
  • The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.0.6001.2229914,84831-Oct-200801:23x86
Msiscsi.sys6.0.6001.22299179,97631-Oct-200803:43x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.0.6001.2229914,84831-Oct-200802:45x64
Msiscsi.sys6.0.6001.22299213,76831-Oct-200805:06x64
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Iscsilog.dll6.0.6001.2229914,84831-Oct-200802:46IA-64
Msiscsi.sys6.0.6001.22299491,78431-Oct-200805:01IA-64

↑ 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

For more information about iSCSI Specification RFC 3720, visit the following Internet Engineering Task Force (IETF) Web site:
https://www.ietf.org/rfc/rfc3720.txt
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


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

↑ Back to the top

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

File namePackage_for_kb959384_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,367
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_client~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,431
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,421
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,423
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,425
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,431
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,422
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum
File versionNot Applicable
File size1,429
Date (UTC)05-Nov-2008
Time (UTC)02:11
File nameX86_iscsi.inf_31bf3856ad364e35_6.0.6001.22299_none_3cf517b30d052ea7.manifest
File versionNot Applicable
File size2,250
Date (UTC)05-Nov-2008
Time (UTC)02:47

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

File nameAmd64_iscsi.inf_31bf3856ad364e35_6.0.6001.22299_none_9913b336c5629fdd.manifest
File versionNot Applicable
File size2,252
Date (UTC)05-Nov-2008
Time (UTC)05:05
File namePackage_for_kb959384_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,375
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,439
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,429
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,431
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,433
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,439
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,430
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,437
Date (UTC)05-Nov-2008
Time (UTC)02:11

Additional files for all supported Itanium-based versions of Windows Server 2008

File nameIa64_iscsi.inf_31bf3856ad364e35_6.0.6001.22299_none_3cf6bba90d0337a3.manifest
File versionNot Applicable
File size2,251
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,425
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,426
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,429
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_server~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,434
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,426
Date (UTC)05-Nov-2008
Time (UTC)02:11
File namePackage_for_kb959384_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum
File versionNot Applicable
File size1,433
Date (UTC)05-Nov-2008
Time (UTC)02:11

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 959384
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 208