I'm running Open-E DSS v6 and with the last re-install of the VMWare ESX and ESXi servers I found the discovery of the targets no longer to work.
No CHAP authentication, nor IP restrictions apply to the test-target.
I was able to work around this issue by using full target names in the ESX(i) kickstart scripts.
Today I set out to fix this probleme and experienced similar problems connecting to iSCSI targets using Microsoft iSCSI Initiator (Windows 2008 R2 default) and Starwind iSCSI Initiator (latest version).
I found that the Open-E server is not listening on port 3260: only 21, 80, 139 and 445 are open.
Sorry for the quick follow up on my own post - I was mistaken with the port scan.
It seems port 3260 is open, but there is no response to any Initiator.
With the MS Initiator I get "Authentication failed" and Starwind says that the port is not opened.
I've turned off the firewall on the initiator machine and I was able to ping both ways.
Furthermore, the ESX machine that has an active session to the DSS on port 3260 does not "discover" the new volume that I've made available to the appropriate CHAP user.
So, I should formulate more precisely: it is not port 3260 that is the problem, but somehow the target discovery is not working.
Is it possible I've accidentally turned it off at some point?
Just checked: No IP controls are in place, and even the MS iscsi command line returned Authentication Failure on the command "iscsicli qaddtargetportal FQDN"