I can't get user validation via SAMBA to work... What can I have missed? I have a domain controller running SLES9 that carries all our user accounts. I'm setting up 9.3 as a client, and I mark user validation SAMBA, join the domain, but still no users on the domain controller can log on to the 9.3 desktop. Anders.
Anders Norrbring wrote:
I can't get user validation via SAMBA to work... What can I have missed? I have a domain controller running SLES9 that carries all our user accounts.
I'm setting up 9.3 as a client, and I mark user validation SAMBA, join the domain, but still no users on the domain controller can log on to the 9.3 desktop.
Did you look into the logfile on the domain controller? What errors are logged there? What is the content of /etc/nsswitch.conf? Is nscd running? If so, shut it down. Sandy
Anders Norrbring wrote:
I can't get user validation via SAMBA to work... What can I have missed? I have a domain controller running SLES9 that carries all our user accounts.
I'm setting up 9.3 as a client, and I mark user validation SAMBA, join the domain, but still no users on the domain controller can log on to the 9.3 desktop.
Did you look into the logfile on the domain controller? What errors are logged there? What is the content of /etc/nsswitch.conf? Is nscd running? If so, shut it down.
Nothing at all in the log files on the SLES9 PDC, the 9.3 workstation's nscd is switched off, and it's nsswitch.conf contains this; passwd: compat winbind group: compat winbind hosts: files lwres dns networks: files dns services: files protocols: files rpc: files ethers: files netmasks: files netgroup: files publickey: files bootparams: files automount: files nis aliases: files Anders.
Anders Norrbring wrote:
Did you look into the logfile on the domain controller? What errors are logged there? What is the content of /etc/nsswitch.conf? Is nscd running? If so, shut it down.
Nothing at all in the log files on the SLES9 PDC, the 9.3 workstation's nscd
On the PDC the services winbind, smbd and nmbd should run. NSCD seems to hinder winbind, so he should be shut down on the PDC.
is switched off, and it's nsswitch.conf contains this;
passwd: compat winbind group: compat winbind
Looks okay. How did you integrate the workstations into the domain? I usually have the task to integrate a linux box into a windows domain. Sandy
Anders Norrbring wrote:
Did you look into the logfile on the domain controller? What errors are logged there? What is the content of /etc/nsswitch.conf? Is nscd running? If so, shut it down.
Nothing at all in the log files on the SLES9 PDC, the 9.3 workstation's nscd
On the PDC the services winbind, smbd and nmbd should run. NSCD seems to hinder winbind, so he should be shut down on the PDC.
is switched off, and it's nsswitch.conf contains this;
passwd: compat winbind group: compat winbind
Looks okay. How did you integrate the workstations into the domain? I usually have the task to integrate a linux box into a windows domain.
I found one thing, the SLES9 didn't run winbind. Works fine anyway for joining by Windows XP clients. They validate users perfectly fine to it. To integrate the 9.3 box I did it at install time, when asked for how I should validate users, I marked SAMBA, then I was asked to join the domain, that I did. Then all the rest, finally a complete reboot and only root could log in, noone stored on the SLES9 could log in. Anders.
Anders Norrbring wrote:
Did you look into the logfile on the domain controller? What errors are logged there? What is the content of /etc/nsswitch.conf? Is nscd running? If so, shut it down.
Nothing at all in the log files on the SLES9 PDC, the 9.3 workstation's nscd
On the PDC the services winbind, smbd and nmbd should run. NSCD seems to hinder winbind, so he should be shut down on the PDC.
is switched off, and it's nsswitch.conf contains this;
passwd: compat winbind group: compat winbind
Looks okay. How did you integrate the workstations into the domain? I usually have the task to integrate a linux box into a windows domain.
I found one thing, the SLES9 didn't run winbind. Works fine anyway for joining by Windows XP clients. They validate users perfectly fine to it.
To integrate the 9.3 box I did it at install time, when asked for how I should validate users, I marked SAMBA, then I was asked to join the domain, that I did. Then all the rest, finally a complete reboot and only root could log in, noone stored on the SLES9 could log in.
Still doesn't work.. On the workstation i get a note in log.winbindd: May 2 11:47:43 siri-lnx pam_winbind[16275]: request failed: No such user, PAM error was 10, NT error was NT_STATUS_NO_SUCH_USER On the domain controller I only have one single reference to the workstation, it's in /var/log/YaST2/y2log: 2005-05-02 11:35:07 <1> beata(18632) [Perl] modules/Users.pm(Users::CommitUser):3139 commiting user 'siri-lnx$', action is 'add_user', modified: 0, ldap modified: 1 Anders.
participants (2)
-
Anders Norrbring
-
Sandy Drobic