CHAP system broke in 6.6.1, saw there was 6.7.0, but it was removed. Now installed 6.7.1, but CHAP still doesn't seem to be working. Keeps saying it is failing the authentication and I don't see anything in the release notes that this was fixed. Is this going to be fixed? Any ETA?
I sent in the logs. I also have another system that was still on 6.6.1 and is failing to authenticate using CHAP. I can send you those logs too if you need more.
kernel: CHAP user or password not set for Initiator ACL
kernel: Proposer's value list "None" contains no valid values from Acceptor's value list "CHAP".
Yes, we know, it doesn't work anymore. We have two of them doing this since the upgrade to 6.6.1. One we tried to fix before the upgrade to 6.7.1, but couldn't get it to work and when 6.7.1 came out, we had hoped it would have been fixed. We at least got the initiator to start working, but only by disabling CHAP. The other one we tried to upgrade from 6.6.1 to 6.7.1 without making any changes, but after the upgrade, we had to disable CHAP on this one too in order to get the connection to reestablish itself.
I would have thought we would have had more reports if this was a widespread issue rather than simply something wrong with your settings. Have you double checked your settings?
Doing a Google search showed me plenty of reports. However, I doubt there are that many people setting up their ReadyNAS using iSCSI and CHAP. As for the settings, we didn't change them after doing the firmware update until we saw that CHAP was no longer working as it was before the update. Again, this has happened on two different systems that are at two different locations and have nothing to do with each other.
Yes, it will detect it and connect to it, but when the Windows System State tries to back up to it, it fails. So far we have found disabling CHAP allows the back ups to succeed.
