Initiator system locks up on full access CHAP authentication

[jeffdgr8]

I installed iStorage Server on a Windows 7 system and created a physical disk bridged target to a 6TB RAID volume. I was able to connect to the target from a Windows Server 2008 R2 system in read-only mode just fine. But when I enabled CHAP authentication to get full access, the Windows Server system locks up any window that has anything to do with viewing the hard disk (i.e. explorer, disk management, iSCSI initiator, etc.) and the entire system fails to even shutdown correctly unless the iStorage Server service is stopped on the Windows 7 machine, which forces the Windows Server to disconnect eventually. The disk starts to become visible. You can just catch it pop up in disk management and it has the correct size. It even assigns it a drive letter and it shows in explorer, but the volume label is never correctly read and if you let it try for long enough messages suggesting to format the disk pop up. The disk is already formatted and contains a lot of data, all of which is visible and readable when connected without CHAP authentication in read-only mode. I also noticed that the IP filter is not doing anything to prevent specific systems from connecting either.

[Olivia (staff)]

Hi,

This is a known issue for the product, windows 7 is not covered. We will resolve this problem as soon as possible (Before the end of the month).
In windows7:
Disk Bridged Device can't provide write access to initiators.
Parition Bridged Device can't provide write access to initiators until the "Hold and Update Support" option is selected.

There are no other compatibility issues.

[jeffdgr8]

Great, good to know it's getting taken care of. Thanks for your help.

[jeffdgr8]

I am experiencing the same problem while using Vista x64 for the target and Windows Server 2008 R2 as the initiator. I tried both the x64 and x86 installs for iStorage Server 1.43. It works fine, however, while using Vista x86 for the target and Vista x64 as the initiator.

[Aldrich]

This problem has been fixed in new version, please pay attention to http://kernsafe.com/forum/viewtopic.php?f=5&t=152