NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
iscsi won't authenticate / reconnect to w2k8r2 x64 host
hi,
looks like a lot of people are having similar issues to mine, but i don't see any solutions.
i created an iscsi share on my RNDP6000 running .19 code. it worked fine for several months, but now will not reconnect at all (i'm getting authentication errors). this started happening after a recent batch of MSFT updates, so i'm wondering if that may be the root of the issue.
at any rate, i need to get it reconnected so i'm hoping someone can make some suggestions on how to get it working again.
TIA for any/all help
D
looks like a lot of people are having similar issues to mine, but i don't see any solutions.
i created an iscsi share on my RNDP6000 running .19 code. it worked fine for several months, but now will not reconnect at all (i'm getting authentication errors). this started happening after a recent batch of MSFT updates, so i'm wondering if that may be the root of the issue.
at any rate, i need to get it reconnected so i'm hoping someone can make some suggestions on how to get it working again.
TIA for any/all help
D
7 Replies
Replies have been turned off for this discussion
- fyi,
i followed the instructions located here :
http://www.readynas.com/?page_id=809
which by the way are no longer correct for w2k8..
everything is correct, but i still get authentication errors.
i think a MSFT patch broke something... - just for giggles, i tried disabling chap authentication, and tried again.
it now works, so the problem is clearly that something has changed with chap and the nas with the patches. - I just checked a 2008 and a 2008r2 system(ran windows update about an hour ago), neither are having an issue connecting to an iSCSI target with CHAP enabled using the windows initiator.
Have you verified that you don't have some sort of network connectivity issue going on? Grievous wrote: I just checked a 2008 and a 2008r2 system(ran windows update about an hour ago), neither are having an issue connecting to an iSCSI target with CHAP enabled using the windows initiator.
Have you verified that you don't have some sort of network connectivity issue going on?
Grievous, not sure how NW connectivity could be the culprit here when just turning CHAP authentication off "fixes" the problem and the connection comes up, stays up, and is rock solid. i've also been hammering the connection doing a level 0 backup for the last few days, and it seems to be reliable at this time.- Couldn't tell ya, but it's certainly worth looking into. If it were a matter of Windows update breaking things(we all know Microsoft isn't exactly known for great documentation of updates), I'd see the same result.
Grievous wrote: Couldn't tell ya, but it's certainly worth looking into. If it were a matter of Windows update breaking things(we all know Microsoft isn't exactly known for great documentation of updates), I'd see the same result.
good point..
aside from creating a new user name / pw, and making sure i cut and paste them on both sides to eliminate any fat finger mistakes, any other suggestions on what to test?- Check the network errors tab before and after copying a large batch of data, still have to eliminate the possibility that it was only barely working in the first place due to network problems. The only other thing that comes to mind is something specifically blocking the CHAP traffic, which would be a little odd. Do you have another client machine to try and connect with using CHAP?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
