Can not Log in Linux with Windows user

I have recently upgraded my system from Samba 2.7 to Samba 3.0.2a

I am on a 2K Domain running in mixed mode named FLORIDA and I was able to add my Linux system (MDKFTP) successfully to the domain.  It is recognized in Network Neighborhood, and when I double click on it asks me to authenticate.  When I try to put in my Windows username (FLORIDA\dthomas or FLORIDA+dthomas) and password it does not authenticate.  When I checked auth.log it displayed the following:

pam_winbind[21813] request failed: Access Denied, PAM error was 4, NT_Status_Access_Denied
pam_winbind[21813] internal module error: (retval = 4, user = FLORIDA\dthomas)

I am trying to share this directory with Windows:  /var/ftp/ftp/

The following functions work on MDKFTP:

wbinfo -t  : It says that the secret is good
wbinfo -g: It shows all the groups in AD
wbinfo -u: It shows all the users in AD
getent passwd: It shows all the users
getent group: It shows all the groups


      log file = /var/log/samba/log.%m
      character set = ISO8859-15
      socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
      wins server =
      encrypt passwords = yes
      # winbind use default domain = yes
      # winbind separator = +
      winbind uid = 10000-20000
      winbind gid = 10000-20000
      template shell = /usr/sbin/scponlyc
      dns proxy = No
      server string = Samba Server %v
      password server = *
      winbind enum users = yes
      winbind enum groups = yes
      local master = No
      template homedir = /var/ftp//ftp
      workgroup = FLORIDA
      os level = 18
      max log size = 50

      comment = FTP folder
      inherit permissions = yes
      path = /var/ftp/ftp
      write list = @FLORIDA\MDKFTP_W
      inherit acls = yes


passwd:     files winbind nisplus nis
shadow:     files winbind nisplus nis
group:      files winbind nisplus nis

#hosts:     db files nisplus nis dns
hosts:      files winbind dns nisplus nis

# Example - obey only what nisplus tells us...
#services:   nisplus [NOTFOUND=return] files
#networks:   nisplus [NOTFOUND=return] files
#protocols:  nisplus [NOTFOUND=return] files
#rpc:        nisplus [NOTFOUND=return] files
#ethers:     nisplus [NOTFOUND=return] files
#netmasks:   nisplus [NOTFOUND=return] files    

bootparams: nisplus [NOTFOUND=return] files

ethers:     files
netmasks:   files
networks:   files
protocols:  files
rpc:        files
services:   files

netgroup:   nisplus

publickey:  nisplus

automount:  files nisplus
aliases:    files nisplus



auth       required      /lib/security/
auth         sufficient      /lib/security/
auth         sufficient      /lib/security/ use_first_pass
auth       required      /lib/security/ service=system-auth
auth       required      /lib/security/
account         sufficient      /lib/security/
account    required      /lib/security/ service=system-auth
password   required      /lib/security/ service=system-auth
session    required      /lib/security/ service=system-auth
session    optional      /lib/security/

auth       required     /lib/security/ onerr=fail item=user sense=allow file=/etc/concord/loginusers


auth       required      /lib/security/ shadow nullok
auth         sufficient      /lib/security/
auth       required      /lib/security/
account    required      /lib/security/
account         sufficient      /lib/security/
password   required      /lib/security/
password   required      /lib/security/ shadow nullok use_authtok
session    required      /lib/security/
session    optional     /lib/security/


auth         required      /lib/security/
auth       required      /lib/security/
auth         sufficient      /lib/security/
auth       required      /lib/security/ use_first_pass shadow nullok
account    required      /lib/security/
session    required      /lib/security/ service=system-auth



auth        required      /lib/security/
auth        sufficient    /lib/security/
auth        sufficient    /lib/security/ likeauth nullok use_first_pass
auth        required      /lib/security/

account     sufficient    /lib/security/
account     required      /lib/security/

password    required      /lib/security/ retry=3
password    sufficient    /lib/security/ nullok use_authtok md5 shadow
password    required      /lib/security/

session     required      /lib/security/ skel=/etc/skel/ umask=0022
session     required      /lib/security/
session     required      /lib/security/

Any help would be much appreciated.

Thank you

Who is Participating?

Improve company productivity with a Business Account.Sign Up

parkerigConnect With a Mentor Commented:

On my box there is a directory of examples.

find / -name smb.conf

Try using and editing one of them.
I would start with the one that says simple.

For testing I always make myself root equivalent in the smb.conf file and do a real simple share eg

   comment = Share to give files to Third Party
   path = /home/exceed/interface
   read only = no
   writeable = yes
   public = yes
   guest ok = yes

In the past when I have had probelms it was normally because the files created at unix level or directory created at unix level had permissions that the guest user couldn't use.

So for testing make sure the directory is chmod 777 /testing and the files init are xwrxwrxwr - for simplicity.

Once all ok then add the required security

I hope this helps a bit
richiemarshallConnect With a Mentor Commented:

It sounds like a pam/winbind issue to me. I recently setup samba 3 on debian and was having very similar issues. I can't remember exactly what I did to resolve the issue, but it did involve modifying the pam settings.

Looking at the settings that I have;
pam.d/login has:
auth       sufficient
account    required
session    required skel=/etc/skel umask=0077

pam/samba has account sufficient not account required.
I also have an entry session sufficient in my common-session settings (sorry, debian does it a little differently) and I couldn;t see an equivalent in your settings.

Hope this makes sense, and helps!

No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:
Split: parkerig{http:#10755817} & richiemarshall{http:#10783542}

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

EE Cleanup Volunteer

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.