On 1/28/07, Rick McNeal <[EMAIL PROTECTED]> wrote:
Could you gather a network trace and send it to me or make it available on the net?
# snoop -o ms-iscsi-2_03.snoop tcp port 3260 http://eric.5amsoftware.com/~eric/ms-iscsi-2_03.snoop.gz In the trace, I am "logging on" to the target with the Microsoft initiator, and then opening Computer Management -> Disk Management.
From there, I see my disk, and I am right-clicking it and then
clicking "open", in order to bring it up in Explorer. It errors out with being unable to open the drive. The following error is reported in Event Viewer: Target sent an invalid status sequence number for a connection. Dump data contains Expected Status Sequence number followed by the given status sequence number. 0000: 00 00 08 00 01 00 62 00 ......b. 0008: 00 00 00 00 2a 00 00 c0 ....*..À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 2a 01 00 00 2c 01 00 00 *...,... It then also logs a reconnection. We're not using mpio, security, or anything fancy here; just plain defaults. Hope this helps, and let me know if there is anything else you would like me to try. Regards, Eric
On Jan 28, 2007, at 6:57 PM, Eric Enright wrote: > On 1/27/07, Eric Enright <[EMAIL PROTECTED]> wrote: >> On 1/27/07, Rick McNeal <[EMAIL PROTECTED]> wrote: >> > Okay, I've uploaded the SUNWiscsitgtr and SUNWiscsitgtu packages >> > which have the fix which prevented the Microsoft Initiator from >> > connecting to the Solaris iSCSI Target. They can be found at: >> <snip> >> >> I've just finished testing the new packages out, and things seem to >> work just fine. I've just done basic connections, though, no CHAP or >> anything. >> >> Thanks, Rick! > > Looks like I spoke too soon. > > When tested above, I used Windows XP Professional. I created a 2GB > volume, and used MS's initiator version 2.03 to attach, format, and > mount it. I then copied some files around and destroyed the volume. > > Today I tested with Windows 2000 SP4, and ran into problems. I can > attach and format the volumes, but they never get mounted to a drive > letter. While they are visible in Computer Management, they are not > visible to Explorer. The following is logged in the Event Viewer: > > Target sent an invalid status sequence number for a connection. Dump > data contains Expected Status Sequence number followed by the given > status sequence number. > > 0000: 00 00 08 00 01 00 62 00 ......b. > 0008: 00 00 00 00 2a 00 00 c0 ....*..À > 0010: 00 00 00 00 00 00 00 00 ........ > 0018: 00 00 00 00 00 00 00 00 ........ > 0020: 00 00 00 00 00 00 00 00 ........ > 0028: 6e 00 00 00 6f 00 00 00 n...o... > > Following that, there is a message about reconnecting to the device > successfully. Looking into my XP logs, I see the same, but they only > seem to appear when formatting/mounting the disk and not really > afterwards. Windows 2003 Server R2 functions the same as Windows XP. > > I've tried this on two Windows 2000 machines, both with the same > issue. I can capture some traffic and make available if requested. > > Has anyone else tried this with Windows 2000? > > -- > Eric Enright ---- Rick McNeal "If ignorance is bliss, this lesson would appear to be a deliberate attempt on your part to deprive me of happiness, the pursuit of which is my unalienable right according to the Declaration of Independence. I therefore assert my patriotic prerogative not to know this material. I'll be out on the playground." -- Calvin
-- Eric Enright _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
