4.01b1-p1-T68 can't access CIFS share via UNC path on Vista

[LuckMan212]

I have a RN1100 using RAIDiator 4.01b1-p1-T68. Security mode is set to "User". When we create CIFS shares on this machine, they are not accessible from Vista workstations. For example, if I create a share called "pub", I can access it just fine from XP/2000 machines by clicking start->run and typing

\\nas\pub

At which point I will be prompted for username and password and then I am able to browse the shares.

On the Vista box, I get the following dialog box:


Any ideas?

[LuckMan212]

Nobody has seen this before? I will add another piece of information, the computers on this LAN are part of a Windows 2003-server domain (Active Directory). However I have chosen not to put the ReadyNAS in AD mode because in my experience it is too much trouble to configure accounts this way and we use the NAS as a kind of public server as well to distribute files to outside vendors and I don't want to add "dummy" domain accounts for non-employees.

Anyway, the non-Vista machines can access these shares no problem so I am sure it's some problem with either Vista or with the CIFS daemon on the nas. Help!

[DougLorenz]

You might try this...

Run secpol.msc
Go to: Local Policies > Security Options

Find "Network Security: LAN Manager authentication level"
Change Setting from "Send NTLMv2 response only" to
"Send LM & NTLM - use NTLMv2 session security if negotiated"

Vista defaults to only send the more secure NTLMv2 protocol, which causes problems with a lot of Samba based NAS devices...

[DougLorenz]

BTW, remember to post to tell me if that works...

[LuckMan212]

Hmm, that is certainly interesting. Seems like that could definitely be the cause of the problem. Come to think of it, I remember reading about the strict NTLMv2 requirement enforced under Vista, but it didn't occur to me this time. I will try it tomorrow at work and definitely post back the results. I wonder if there is a fix for linux-based (samba) that could support NTLMv2 so these Vista desktops would not have to have their Group Policies manually fixed? I suppose I could push out this change via Active Directory but I'd prefer if it worked "out of the box".

[goldcd]

I'd made the network security change a while back as I was having problems with my shares and it seemed to sort out the problem.
Currently running T68 beta and repeated what you did to get the error on Vistax64 and it worked fine for me.