It may be useful if you could use the checked build of the Microsuft iSCSI initiator. This allows you to create a debug log file as well as send debug logging to a kernel debugger. You can read up on this in this document: "Microsoft iSCSI Software Initiator User's Guide 2.x" http://download.microsoft.com/download/a/e/9/ae91dea1-66d9-417c-ade4-92d824b871af/uguide.doc See the section on "Debug Logging"
You need to set up a value in the registry, to enable the logging. I used the value they recommend: DebugSpewLevel of 0x006f0007 You can download the checked build version of the initiator here: http://download.microsoft.com/download/0/D/7/0D7CDB5C-74D8-4118-9BE0-DE021EF6F35C/Initiator-2.03-build3099-x86chk.exe When I did this, I first un-installed the normal 'free/retail' build version of the initiator, before installing the checked build version. To can view the debug ouput with a program called "DebugView" available here: http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx Note that the checked build version of the initiator is for troubleshooting only, and not for use in production environments. Ok, if you try this & see anything interesting logged in the DebugView output, at the time the connection aborts, then post that back to the forum. From what you describe, it looks to me like this problem only occurs when the Windows PC is under heavy stress. Thanks Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
