Hi all -
I have an odd issue using smbclient to connect to a Windows 2000 and a Windows XP machine.
$ smbclient //machine/service -U my_user_id%my_password
Domain=[DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
and then I can browse directories, perform 'ls', 'cd', 'get', etc. commands.
However, as part of my network backup, I also use the tar functionality of smbclient, and that doesn't work so well:
$ touch /tmp/flag
$ smbclient //machine/service -U my_user_id%my_password -TcN /tmp/flag ./test.tar
Getting files newer than Tue Apr 18 09:57:10 2006
session setup failed: NT_STATUS_LOGON_FAILURE
and I know it's a valid user ID and password because it's the same one I used in the prior command. Same behaviour occurs under Windows 2000 and Windows XP. The user ID is in the Administrators group on both the 2000 and XP boxes, and has inherited permissions to read everything on the share.
The system event viewer on the XP box shows:
Reason: Unknown user name or bad password
User Name: my_user_id
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NWV1_0
Workstation Name: WORKSTATION
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Same results if I store the user ID and password in a file and then use the -A flag on the smbclient command line.
Interestingly, if I only log in with the user ID (so that smbclient will prompt me for the password), it works as expected in interactive mode, but in tar mode, it never prompts me for a password
-- it just fails right away.
The tar functionality worked under FC3 (don't know which version of the Samba suite), but fails under FC5 (smbclient --version returns Version 3.0.22-1.fc5). I'm wondering if maybe something changed in the Samba suite that affects the way it authenticates in interactive mode, vs. what it does in 'tar' mode.
Me confundo mucho ...