Ok, Jim. Thanks for the post to the Forum. Sorry to hear you are having the same problem. Let's work together on this & try to get to the source of the problem.
Normally a packet capture is useful. But in this case, where the problem is occurring during a file copy, I think it's going to be like looking for a needle in a haystack. That does not mean impossible, just difficult. How often is the error occurring? Typically what is the time period between error? Are you getting the same Event log errors as Eric reported? Are the errors occurring in bursts? Obviously the capture file needs to be from the period when the error is occurring. But if you capture too much before or after the errors we will have a very big capture file! It would help if the file format of the capture file recorded the true time of the packets, like Ethereal does, rather than just an offset from some arbitrary start time, like snoop does. So maybe you could try capturing with Ethereal running on your Windows server. And then also note for me the times of errors shown in the event log. That way we should be able to match up the times in capture file to those in the event log. I will send you my Gmail email address as that is better for sending large files. Alternatively, maybe you could upload the capture file to a web site. I still feel strongly that using the checked build version of the Microsoft iscsi initiator would be very useful, for the reason given in my previous post. URL's to download the checked build for the v2.06 release are given here: http://www.microsoft.com/downloads/details.aspx?familyid=12cb3c1a-15d6-4585-b385-befd1319f825&displaylang=en (Note that Microsoft say you should be running with at least SP4 if you are still using Windows 2000.) Best Regards Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
