Not listening on port 3260

[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)...

[Gr-R]

can you tell the MS initiator to look at the DSS IP, or have you done this?

in vmware, dynamic discovery can be disabled, if you are using static discovery.

[Arcesilaus]

Thank you for your reply!

I've tried by IP, using two machines on different subnets that both could ping the DSS (and vice versa), and FQDN.

I probably disabled the dynamic discovery in VMWare (is it by default? I never checked, since I install by kickstart script and use static discovery there), but I cannot see how that would be the cause the MS discovery authentication failure.

Any other ideas?

[Arcesilaus]

Am I the only one experiencing difficulties with Microsoft's native iSCSI?

[Gr-R]

See if you can telnet to the port and get an answer.
There isnt anything on the DSS side that would block it. In fact DSS will broadcast the LUN on each IP assigned to it.
You can try to remove the target and re-add it. This will not remove data, just don't delete the Volume.

I suspect something is blocking traffic in between the initiator and the LUN.

[To-M]

At this point maybe a remote viewing might help. Can you send me an email via the forum and I will tell what to do next.

[Arcesilaus]

Thanks Todd for your assistance.

I will make one last attempt before calling for your help: I will shutdown the ESX, reboot the DSS machine so it runs the latest updates and no connections are running and try to connect.

If the cert issue (weird: removing the root from the trusted authorities in my personal store gets me to the login, but no further?) has been fixed, I will download some logs.

Will get back to you soon...

[To-M]

Make sure after rebooting the ESX server to use the reset function for the iSCSI Targets in Location
MAINTENANCE -> connections -> Function: iSCSI connection reset.