Open Software Solutions

Consider the following scenario:

•	You are running a Windows Server 2008-based computer.
•	You establish an iSCSI session on this computer.
•	In the iSCSI session, you click to select the Automatically restore this connection when computer starts check box.

After you restart the computer, you expect the Microsoft Software Initiator to automatically log on and to make the logical unit numbers (LUNs) available without requiring you to manually create an iSCSI session. However, this feature may not work as expected if you are using Challenge Handshake Authentication Protocol (CHAP) authentication.

Back to the top

This problem may occur because the encrypted CHAP secret may be corrupted in memory after it is read from the registry on a Windows Server 2008-based computer.

Back to the top

Hotfix information

A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2008 Service Pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, you must have Windows Server 2008 installed.

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 Server 2008, x86 version

File name	File version	File size	Date	Time	Platform
Package_1_for_kb951058~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,805	29-Apr-2008	21:12	Not Applicable
Package_2_for_kb951058~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,972	29-Apr-2008	21:12	Not Applicable
Package_3_for_kb951058~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,810	29-Apr-2008	21:12	Not Applicable
Package_4_for_kb951058~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,810	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,421	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,429	29-Apr-2008	21:12	Not Applicable
X86_iscsi.inf_31bf3856ad364e35_6.0.6001.22168_none_3d1485470cedc456.manifest	Not Applicable	2,250	29-Apr-2008	21:17	Not Applicable
Iscsilog.dll	6.0.6001.22168	14,848	29-Apr-2008	01:40	x86
Msiscsi.sys	6.0.6001.22168	181,304	29-Apr-2008	04:01	x86

Windows Server 2008, x64 version

File name	File version	File size	Date	Time	Platform
Amd64_iscsi.inf_31bf3856ad364e35_6.0.6001.22168_none_993320cac54b358c.manifest	Not Applicable	2,252	29-Apr-2008	21:23	Not Applicable
Package_1_for_kb951058~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,815	29-Apr-2008	21:12	Not Applicable
Package_2_for_kb951058~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,984	29-Apr-2008	21:12	Not Applicable
Package_3_for_kb951058~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,820	29-Apr-2008	21:12	Not Applicable
Package_4_for_kb951058~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,820	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,429	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	29-Apr-2008	21:12	Not Applicable
Package_for_kb951058_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,437	29-Apr-2008	21:12	Not Applicable
Iscsilog.dll	6.0.6001.22168	14,848	29-Apr-2008	02:09	x64
Msiscsi.sys	6.0.6001.22168	215,096	29-Apr-2008	04:24	x64

Windows Server 2008, IA-64 version

File name	File version	File size	Date	Time	Platform
Iscsi.inf	Not Applicable	7,440	28-Apr-2008	22:59	Not Applicable
Iscsilog.dll	6.0.6001.22168	14,848	29-Apr-2008	02:01	IA-64
Msiscsi.sys	6.0.6001.22168	491,576	29-Apr-2008	04:05	IA-64

Back to the top

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

Back to the top

Users and applications request and receive data from high-performance data storage devices over standard network switches and over IP routers. The iSCSI protocol sends SCSI commands that are encapsulated in IP packets over TCP/IP networks. Because iSCSI is IP-based, data can be transmitted over local area networks (LANs), over wide area networks (WANs), and over the Internet to remote storage locations.

Back to the top