Not listening on port 3260

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

[Arcesilaus]

Hi Todd

This is clearly not my best day: I was able to fix the certificate issue by clearing the cache and downloading the SSLcert from the webinterface.

I did a reset of all iSCSI connections and tried again: no luck, still Authentication error.

I then rebooted the server to run with the latest updates, but now it only returns a blank page! No errors on the console and I can see the webserver is running by trying any non-existing path.
I tried on 3 machines, so I guess something is wrong with the update (85).
Let's reboot back into previous state...

[To-M]

Sounds for sure something is acting up. Any chance you can do a fresh install of the DSS V6 on another USB flash stick w/ the previous version like your doing now?

[Arcesilaus]

I recreated a certificate, but a reboot with version 85 gave me a "selftest OK" again, but still a blank screen.

Rebooted into version 80 and I'm back in...

While the ESX was still off, I removed the IP restrictions on all targets, so they were set to "ALL" on "Allowed" and disabled the CHAP authentication for all of them.

But still, no luck with adding the target portal to any MS iSCSI initiator...

[To-M]

Can you post the logs for us to see or to support.

[Arcesilaus]

It has been a while since I've been working on this issue (had to finish my degree first), so I guess it's time for an update:

From version 90 all was working fine again and I am currently running version 97 (latest).
I've been able to reproduce the errors. What appears to be the case?

Any Windows server that has a primary NIC in my LAN and is a domain member, fails when connecting through a dedicated NIC in the iSCSI LAN (or VLAN, in case of a virtual machine).
Contrary, any server that has its primary NIC in another LAN (or VLAN) and subnet, succesfully authenticates, all settings on the DSS being equal.

Now I'm getting really puzzled...