I figured it out.... just wanted to post my answer here just in case anyone else is having the same problem.   While upgrading the firmware on the SAN was important, what resolved the issue was actually upgrading the firmware on my server's NIC card.  In my case, there was a firmware upgrade utility for my HP NC382T NIC in my Proliant DL380 G7 server on HP's support site.  While using the utility, I found that the iScsi portion of the firmware was very out of date, and was prompted to upgrade it.  After upgrading the firmware and reinstalling the drivers for good measure, the iScsi conenction worked perfectly. Thank you everyone for your input!
Hey everyone,About a year ago I was able to re-purpose a PS4000 SAN and an older proliant server to make a small Hyper-V network.  It has always ran great and hasn't given me any problems.  Recently I acquired a second PS4000 and proliant server... so I added the second SAN to the original SAN group with the intention of making a second volume in the group for my second server to use.The problem I'm having is that my second server can seemingly connect to the second volume via iScsi, but once it's connected I can't format the drive or anything.  Attempting to initialize and format the drive just goes on forever, disk management seemingly freezes.  There is an error in the event viewer saying "Target failed to respond in time to a Task Management request."  Additionally the SAN group even log shows the event  "iSCSI session to target was closed. iSCSI intra-group connection failure. Reset received on the connection.If anyone could give me some insight on this it would be greatly appreciated... I'm pretty new to the SAN world.  The only difference between the two servers is that one is Server 2012 and the other one is 2012 R2.
PS4000 group, "Target failed to respond in time to a Task Management request."