[Samba] issues with smbclient 3.0.x against 3.4.x server
lacoste at u-pec.fr
Thu Feb 17 06:39:45 MST 2011
On 16 févr. 11, at 12:59, Thierry Lacoste wrote:
> I'm upgrading my samba installation from 3.0.34 (FreeBSD 6.4)
> to 3.4.x (CentOS 5.5) from SerNet.
> I have LDAP based samba domain (PDC and BDC) and a homes/Profiles
> member server.
> I first upgraded my DCs to 3.4.9 with no problem.
> I have recently installed a new file server (samba 3.4.11 on CentOS
> I have issues connecting to this server with old versions of smbclient
> which give 'session setup failed: NT_STATUS_LOGON_FAILURE'
> with the foolowing command line:
> smbclient //new-server/user -U user
My bad. This has nothing to do with clients. I just need to specify
I found the answer with a log level = 3 on the homes server.
On a client with the smb.conf workgroup parameter unset,
smbclient //new-server/user -U user
is rejected and the server's log shows:
[2011/02/17 15:17:23, 3] libsmb/ntlmssp.c:745(ntlmssp_server_auth)
Got user=[user] domain=[WORKGROUP] workstation=[CLIENT1] len1=24
On a client with the workgroup set to MYGROUP (which is the case on
distributions of samba), smbclient is also rejected and as one could
expect we have:
[2011/02/17 15:09:13, 3] libsmb/ntlmssp.c:745(ntlmssp_server_auth)
Got user=[user] domain=[MYGROUP] workstation=[CLIENT2] len1=24 len2=24
On every client, specifying the domain to which the file server is
smbclient //new-server/user -U user -W MYDOMAIN
AFAICS it was not required to specify the domain with 3.0.x member
Sorry for the noise.
More information about the samba