"SteveK" <SteveK@discussions.microsoft.com> wrote in message
news:793DDDAC-D5CB-41D7-821A-3CC09B2EF34A@microsoft.com...
> "SteveK" wrote:
>
>> in RC2 this forum gave me the following solution to a problem
>> accessing linux
>> devices - i.e. password format was not accepted due NTLM.
>>
>> - Click Start
>> - Click Control Panel
>> - Click System and Maintenance
>> - Click Administrative Tools
>> - Double-Click Local Security Policy
>> - In the left pane, click the triangle next to Local Policy
>> - In the left pane, click Security Options
>> - In the right pane near the bottom, double-click "Network security:
>> LAN
>> manager authentication level"
>> - Click the drop-down box, and click "Send LM & NTLM - use NTLMv2
>> session
>> security if negotiated"
>> - Click OK
>>
>> The solution worked perfectly - BUT now I have a the final version
>> (Vista
>> Home - bought in a shop) I have the same problem except that when I
>> try to
>> follow the procedure above there is no 'Local Security Policy' option
>> in the
>> Administrative Tools section of the control panel.
>>
>> Can anyone tell me where I can access the 'Local Security Policy'
>> settings??
>>
>> Thanks, SteveK
> The implications are it seems that if you have any Linux based NAS
> devices
> (which probably accounts for the majority) they will not work
> (passwords)
> with Vista Home Edition. There are going to be a lot of very unhappy
> people
> out there! You'll have to pay another £144 to upgrade to Ultimate!
>
> Any comments, input, work arounds or donations towards a copy of
> Ultimate
> greatly appreciated.
>
Two thoughts: One, perhaps there is a way to upgrade the NAS devices to
support NTLMv2 authentication. Two, perhaps there are registry settings
that can achieve the same effect as using the Local Security Policy
settings.
In XP Pro, changing from "Send LM & NTLM responses" to "Send LM & NTLM -
use NTLMv2 session security if negotiated" changes
"lmcompatibilitylevel" in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa from
dword:00000000 to dword:00000001
If someone with a Business or Ultimate version had time and inclination,
they could run a registry compare before & after changing the
authentication level and see what surfaces. Unfortunately I don't yet
have access to a copy of Business or Ultimate or I'd do it - I'll
eventually have to anyway so I can automate a couple of deployment
scenarios.
Hope this helps.
Regards,
Dave