The iSCSI Target does not cause this effect. Does this happen with all MS initiators? Also try to delete the iSCSI Volume and re-create it again using Block IO.