I've googled, RTFMed, and I still can't fix this. Hoping someone here can offer a suggestion. I'm learning, so please explain a little if you can. I installed samba on a Ubuntu 5.10 machine (named mog). My XP machine "sees" it, but the username/password dialog fails. I've traced it down to what I think is an authentication problem: mat@mog:/etc/samba$ smbclient -L mog -U mat Password: <I enter my password here> session setup failed: NT_STATUS_LOGON_FAILURE If I replace -U mat with -N I get a typical smbclient -L listing, so I know something is working. Another fact is that I have an older Ubuntu (Hoary) machine that also serves samba and works. I copied its /etc/samba/smb.conf to the machine having trouble; the two machines are the same (config, username, and password). Right now the workgroup names are different on the two machines, but that didn't make a difference. I'm stumped. Mat *************** /etc/samba/smb.conf follows ***************** # Samba config file created using SWAT # from 192.168.0.103 (192.168.0.103) # Date: 2005/12/12 15:40:02 # Global parameters [global] workgroup = ECLIPSE server string = %h server (Samba, Ubuntu) obey pam restrictions = Yes passdb backend = tdbsam, guest passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 dns proxy = No ldap ssl = no panic action = /usr/share/samba/panic-action %d invalid users = root [printers] comment = All Printers path = /tmp create mask = 0700 printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers [homes] valid users = %S read only = No
On Wednesday 14 December 2005 10:12, Mathew D. Watson wrote:> I've googled, RTFMed, and I still can't fix this. Hoping someone here > can offer a suggestion. I'm learning, so please explain a little if you > can. > > I installed samba on a Ubuntu 5.10 machine (named mog). My XP machine > "sees" it, but the username/password dialog fails. > > I've traced it down to what I think is an authentication problem: > > mat@mog:/etc/samba$ smbclient -L mog -U mat > Password: <I enter my password here> > session setup failed: NT_STATUS_LOGON_FAILURE > > If I replace -U mat with -N I get a typical smbclient -L listing, so I > know something is working. > > Another fact is that I have an older Ubuntu (Hoary) machine that also > serves samba and works. I copied its /etc/samba/smb.conf to the machine > having trouble; the two machines are the same (config, username, and > password). Right now the workgroup names are different on the two > machines, but that didn't make a difference. > > I'm stumped.[...] Please follow the official Samba documentation. Suggest you follow the examples and the step-by-step deployment information in the book "Samba-3 by Example". You can purchase hard copy from Amazon.Com, or download the PDF from: http://www.samba.org/samba/docs/Samba3-ByExample.pdf If you have a problem with any step, in any chapter of this book please email me the datails so I can improve the documentation. - John T.
Mathew D. Watson wrote:> I installed samba on a Ubuntu 5.10 machine (named mog). My XP machine > "sees" it, but the username/password dialog fails. > > I've traced it down to what I think is an authentication problem: > > mat@mog:/etc/samba$ smbclient -L mog -U mat > Password: <I enter my password here> > session setup failed: NT_STATUS_LOGON_FAILURE > > If I replace -U mat with -N I get a typical smbclient -L listing, so I > know something is working. > > Another fact is that I have an older Ubuntu (Hoary) machine that also > serves samba and works. I copied its /etc/samba/smb.conf to the machine > having trouble; the two machines are the same (config, username, and > password). Right now the workgroup names are different on the two > machines, but that didn't make a difference. >The solution to this problem is to run (as root): # smbpasswd -a username where username corresponds to a user account that already exists on the samba server. In my case I used mat as the username. This account is on all of my systems, and the login password is the same on all accounts. I'm not sure this is necessary, but I can say it worked. I was tempted to run this earlier, but I didn't for two reasons. First, the official documentation says something about smbpasswd backend being replaced by tdbsam. Second, my old (working system) didn't have an smbpasswd file at the location reported by 'smbd -b', so I figured I hadn't run smbpasswd before (otherwise there'd be an smbpasswd file. right?). Wrong. Running smbpasswd didn't create an smbpasswd file. I guess it's because I specified the tdbsam backend, which must use some-other-place to stash the password data gathered by smbpasswd. Mat