On Tue, Apr 14, 2009 at 4:56 PM, Joseph L. Casale <[email protected]> wrote:
>>I could try that, but I have two other windows 2003 servers connected >>to the SAN right now and are using it fine. > > Could be an issue with just those luns? > I remasked the LUNs to show for an existing (and working) server. The server sees the disk but has the same issue as the other two; can't initialize it. It's still using its existing drive just fine. It's starting to look a lot like an IBM issue at this point. I deleted the LUN, recreated it, added it directly to the "working" server, still same error. >>I'm doing that now. Both servers are running MS Initiator over a >>regular NIC. One of the servers has a Qlogic Fiber HBA in it to >>connect to a Fiber Channel SAN, but is trying to do all iSCSI vial MS >>Initiator. > > I got nothing man :( If it were me, I would still wanna know if the > san was to blame or the servers... > > What NIC and what driver out of curiosity? > > jlc All my NICs are Broadcom, but I'm not sure that's the issue. I'm working with IBM support now, I'll post back the fix when I get it. Thanks Joseph. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
