Hello,  That doesn't sound correct.   However, did you run the remove setup wizard and exclude the non iSCSI SAN subnets?   Did you join an AD domain or change hostname after setting up iSCSI?  Even as a test then add volumes later?    When you connect to a volume, WIndows creates a static entry for that connection using the IQN at the time.  If you later join a domain or change hostname, that static entry isn't updated.  It has old hostname.   The HIT kit does have capability to create a new ACL on the fly if needed.  I.e. you put in only one IP address, it detects the other an creates a CHAP account for other IP on the fly.   What version of EQL firmware and HIT/ME software? Regards,   Don 
I have some non-clustered Windows terminal server VMs running in vmware on an EQ group (ps6000 and ps6210xs). The VMs have iscsi connections to data volumes on the EQ. I'm restricting volume access by IQN of the terminal server hosting it, so I leave the "allow simultaneous connections from initiators with different IQNs" unchecked for those volumes. I started setting up MPIO with HIT/ME a couple of weeks ago, and today I noticed that some of those data volumes now have the "allow simultaneous" box checked. Is that something that happened during the MPIO setup? Is it required, even though it's still only one IQN ( multiple NICs)?
Simultaneous IQN connections