These work arounds have been developed by ourselves and some of our customers perhaps without fully understanding the implications of the solution, and so may not be appropriate for all environments. In other words, your mileage may vary.
 
Also, they are based on the use of the Microsoft iSCSI Initiator version 1.05a
 
If upon reboot your iSCSI luns come up in the "reconnecting" state:
 

 
And you've verified that all of the underlying network is functioning correctly, the following workarounds may alleviate the problem:
 
First log off of all active sessions and remove all persistent targets and target portals.
 
Next re-add portals
 

 

 
But click on the advanced tab to force use of the MSiSCSI initiator and the specific network interface.
 

 
Repeat this process when you first log on to target.
 

 
We used to say Check the multi-path box but that's wrong. Don't check the multi-path box unless you are doing multi-path. In fact, don't even try to use multi-path unless you are using the MS 2.0 or later initiator.
 

 
and force the interface to use.
 

 
Finally, reboot the system to test that the work around did what you wanted it to do.
 
If none of the above clears up you problems, but things work fine if you use a non-alacritech initiator or you disable the Alacritech fastpath driver, then please Contact Alacritech Support