search for: smb_pwd_check_ntlmv1

...rs occur every time I 'touch' a file on the NFS mount via a cron script running on the samba server on each mount from the NAS... [2004/01/29 20:18:00, 0] auth/auth_sam.c:smb_pwd_check_ntlmv2(107) smb_pwd_check_ntlmv2: incorrect password length (9) [2004/01/29 20:18:00, 0] auth/auth_sam.c:smb_pwd_check_ntlmv1(52) smb_pwd_check_ntlmv1: incorrect password length (9) seems to want to map root to Administrator in SFU user mapping - mount is by root, file is touched (updated) and mounts seem to work just fine. Worry or not worry? I am now fully in production usage - things seem to work ok with one except...

...Some important factors: 1. The selected protocol is LANMAN2.1 with either test. 2. When running net password the SessionSetup andX request is done anonymously (the username is blank in the request) but when running net view the SessionSetup andX does include the username in the request. 3. In smb_pwd_check_ntlmv1() the Part Password (P16) is the same in both traces. Then with the failed operation I notice that values logged under 'Password from Client was |' and 'Value from encryption was |' are different, but with the successful operation they are the same. I can also see that the failed...

...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...

...ample shows ~100 lines like that in one second, probably caused by a user running an application that has its data on that share. Often these messages are accompanied by one or two messages like these Mar 20 10:05:01 LS1 smbd[31614]: [2012/03/20 10:05:01.166801, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1) Mar 20 10:05:01 LS1 smbd[31614]: smb_pwd_check_ntlmv1: incorrect password length (64) The <share name>s seen are the only two public writeable shares on the server. Here is smb.conf (global and affected shares) ===== smb.conf begins ===== [global] workgroup = ACUR server string = Serv...

...4 password checking (libsmb/ntlm_check.c:ntlm_password_check(322)) With debug on 100 and DEBUG_PASSWORD on it shows the following: [2004/04/10 22:23:49, 4] libsmb/ntlm_check.c:ntlm_password_check(322) ntlm_password_check: Checking NT MD4 password [2004/04/10 22:23:49, 100] libsmb/ntlm_check.c:smb_pwd_check_ntlmv1(67) Part password (P16) was | [2004/04/10 22:23:49, 100] lib/util.c:dump_data(1864) [000] AB A4 5E 23 42 B3 27 7E 03 0C DB 4F 97 48 B6 0E ..^#B.'~ ...O.H.. Password from client was | [2004/04/10 22:23:49, 100] lib/util.c:dump_data(1864) [000] 22 63 62 8E 2A BD 54 16 D1 0F EE 6C 0...

I have a Samba 3.4.7 PDC set up (Ubuntu 10.10/OpenLDAP) and have configured a Windows 7 Pro 64 bit workstation as a domain member. Logins and shares work without a hitch. I'm running into a problem with ArcGIS 10 Server on Windows using domain accounts for the services. ArcGIS post-install fails because it won't take the username/password combination of the domain account. I initially