Prev: net rpc rights grant: NT_STATUS_ACCESS_DENIED
Next: [Samba] NT_STATUS_BAD_NETWORK_NAME
From: raichea on 5 Sep 2009 07:40
I have a Linux server providing file and print services to a small
network of XP systems. The printer and most of the shares are available
to all as read-only. One particular share is used by the XP
Administrator accounts (mapped to root) to hold XP backup data. This has
been working fine for the last couple of years.

A new system added to the network runs Vista Home Premium and along with
many others (from googling around), I cannot get write access for the
Admin account to work. My research has determined that this is due to
Vista's use of NTLMv2 and there are many sites that recommend tweaking a
Vista registry setting to put things back to normal by downgrading the
authentication mechanism to that of XP, but that seems the wrong
approach to me.

Samba (I'm running 3.2.7 on Suse 11.1) supports NTLMv2 from what I've
read, but it doesn't seem to be attempting to use this protocol if I'm
interpreting the smb.log output correctly - I see entries like this:


[2009/09/05 12:22:15, 0] libsmb/ntlm_check.c:smb_pwd_check_ntlmv1(54)
smb_pwd_check_ntlmv1: incorrect password length (68)

but no reference to NTLMv2.

I've checked the smb.conf docs but can't see anything that looks
particularly relevant - there are commands to disable the lower forms of
authentication, but it seems that NTLMv2 should be enabled by default.

Anyone got advice, suggestions... if it comes to it, I can make the
registry hack, but I'd rather do things the "proper" way.

Thanks for reading, Steve.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: net rpc rights grant: NT_STATUS_ACCESS_DENIED
Next: [Samba] NT_STATUS_BAD_NETWORK_NAME