Kelvin Leung
asked on
"Authentication failure" error when adding an iSCSI target with CHAP in Windows 2008R2 Server
Hi all,
I would like to get some help from you guys about connecting to an iSCSI target portal in Windows 2008R2 Server using iSCSI initiator.
I have several NAS's (QNAP's and Synology) in my dept and I would like to connect to them via iSCSI with CHAP enabled. I can only connect to them without CHAP turned on but I can't if I enabled CHAP and I am getting the "authentication failure" error for some reason. The secret password is 16 characters long (letters and numbers only). I don't have IPSec enabled and I don't have mutual CHAP enabled as well. I make sure the login information matches on both NAS and iSCSI initiator. I have tired to connect these NAS's from other systems none of them can connect to them with CHAP enabled.
Can someone walk me through the troubleshooting steps?
Thanks.
I would like to get some help from you guys about connecting to an iSCSI target portal in Windows 2008R2 Server using iSCSI initiator.
I have several NAS's (QNAP's and Synology) in my dept and I would like to connect to them via iSCSI with CHAP enabled. I can only connect to them without CHAP turned on but I can't if I enabled CHAP and I am getting the "authentication failure" error for some reason. The secret password is 16 characters long (letters and numbers only). I don't have IPSec enabled and I don't have mutual CHAP enabled as well. I make sure the login information matches on both NAS and iSCSI initiator. I have tired to connect these NAS's from other systems none of them can connect to them with CHAP enabled.
Can someone walk me through the troubleshooting steps?
Thanks.
ASKER
Thanks for your response, dlethe.
Yes, I have read this and followed the instruction step-by-step. In fact, I was able to connect to the same NAS with CHAP enabled before we shut down our servers and NAS's for a power outage over the weekend (we shut down everything gracefully before the power outage). But we can no longer connect to any of them with CHAP enabled after we brought up the NAS's and servers on Monday for whatever reason. I can only connect to them if I turned off CHAP. Do you have any idea what might cause this? Any tips for me to troubleshoot this problem?
Thanks again for your effort.
Yes, I have read this and followed the instruction step-by-step. In fact, I was able to connect to the same NAS with CHAP enabled before we shut down our servers and NAS's for a power outage over the weekend (we shut down everything gracefully before the power outage). But we can no longer connect to any of them with CHAP enabled after we brought up the NAS's and servers on Monday for whatever reason. I can only connect to them if I turned off CHAP. Do you have any idea what might cause this? Any tips for me to troubleshoot this problem?
Thanks again for your effort.
No suggestion other than calling the hardware vendors. iSCSI stacks are notorious for incompatibility issues, so you really need to talk to the hardware vendors and see which ones they have qualified, and get the appropriate settings.
This isn't anything you can typically debug yourself because the specs are just too fuzzy and way too many variables.
So really my "official" response is that people can't generally diagnose iSCSI security/connection issues themselves because they don't have access to the source code and the requirements within the hardware / software stacks on both sides if they don't work out of the box.
You have to run what has been qualified and get all the settings necessary. You may even have to buy a 3rd party iSCSI stack.
This isn't anything you can typically debug yourself because the specs are just too fuzzy and way too many variables.
So really my "official" response is that people can't generally diagnose iSCSI security/connection issues themselves because they don't have access to the source code and the requirements within the hardware / software stacks on both sides if they don't work out of the box.
You have to run what has been qualified and get all the settings necessary. You may even have to buy a 3rd party iSCSI stack.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
exactly what was the answer?
ASKER
The steps were documented right above your last comment. No body knows what was causing it but this was the workaround that the QNAP rep recommended and it works for us.
ASKER
Found my own answer. Administrator, please go ahead and close this thread.
http://web.qnap.com/pro_application.asp?ap_id=135