Not listening on port 3260

[Arcesilaus]

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.

Ports found open on the DSS are:

80
111
139
199
389
443
445
2049
3260
6666-6668
10000
11211

[Gr-R]

firewall?

DSSV6 isn't blocking anything ...

[Arcesilaus]

Thanks for the quick reply.

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?

[enealDC]

Did you add a lun to the iSCSI target? Is the lun # 0? Did you modify any of IP access controls for the target?

[Arcesilaus]

Sorry for the late response: I did not add a new LUN to an existing target, but created a new target instead.

There is no CHAP authentication enabled, but still MS iSCSI control panel reports "authentication failure".

[Arcesilaus]

Just checked: No IP controls are in place, and even the MS iscsi command line returned Authentication Failure on the command "iscsicli qaddtargetportal FQDN"

[Arcesilaus]

The eventviewer reports:

iSCSI discovery via SendTargets failed with error code 0xefff0009 to target portal *192.168.xxx.xxx 0003260 Root\ISCSIPRT\0000_0 .

The MS website (http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx) only explains that it is an Authentication Failure

This is regardless the OS (tried Win 7 and 2008 R2) or machine (tried 2 physical machines and 2 virtual machines)...