Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

  1. #1

    Default After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    A machine with version 13.1 was used as a samba server/FTP server. Clients were Windows7, Ubuntu12.04 (redobackup live-CD) and Tumbleweed machines. All worked well.
    Upgrade of the samba server was delayed because of pam_userdb to pam_pwdfile transfer-problems with vsftpd.
    These have been solved and the samba server now has been upgraded to Tumbleweed as O/S.
    The smb.conf file has been copied and not changed.

    Since the upgrade, Tumbleweed clients can connect to the samba shares as before (via mount.cifs and in Dolphin), but Windows7 machines (in explorer and command line) and machines using redobackup (Ubuntu 12.04, with mount.cifs) get errors (password incorrect).
    The samba user has it's password set with smbpasswd -a smbuser.

    I assume that the security level on the samba server now is too high for Windows7 and Ubuntu12.04, but I don't know how to fix it.

    smb.conf is:
    #start of smb.conf

    [global]
    workgroup = dci-electronics
    usershare allow guests = No
    add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
    domain logons = NO
    domain master = NO
    security = auto
    netbios name = dci-lfs-02
    printcap name = /dev/null
    load printers = no
    ldap admin dn =
    passdb backend = smbpasswd
    wins server =
    wins support = No

    [images]
    comment = hardisk images client pcs
    path = /images
    writeable = yes
    create mask = 0664
    guest ok = yes
    force user = smbuser
    inherit acls = yes
    browseable = yes

    [images2]
    comment = oude hardisk images client pcs
    path = /images2
    writeable = no
    guest ok = No
    force user = smbuser
    inherit acls = yes
    browseable = yes
    read only = Yes

    [LMW]
    comment = LMW documentatie
    path = /smbdata/LMW
    writeable = yes
    create mask = 0664
    guest ok = yes
    force user = smbuser
    inherit acls = yes
    browseable = yes

    #end of smb.conf



    The mount command used is (Tumbleweed and Ubuntu)
    mount.cifs //10.0.0.x/sharename dir -o username=smbuser,password="xxx"
    the net use command used is (Windows)
    net use x: \\10.0.0.x\sharename /user:smbuser

  2. #2
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,728
    Blog Entries
    2

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    I really don't know, but here are some random thoughts.

    Is smbuser a Linux user on the Tumbleweed server?
    (I think you will say "yes")


    Security might drop if you do this
    Try this:
    Code:
    security = user
    And then redo this:
    Code:
    smbpasswd -a smbuser
    These are superfluous I hope:
    Code:
    wins server =
    wins support = No
    But just in case they are doing something, make them like this
    Code:
    ##wins server =
    ##wins support = No
    Then reboot Linux and then reboot Win 7.

    Check that the daemons are running. I think they are or some things would already be not working, but just check anyway, these comnads.
    Code:
    systemctl status nmb.service
    systemctl status smb.service
    Last edited by swerdna; 21-Sep-2017 at 02:49.
    Leap 42.3 & 15.1 &KDE
    FYIs from the days of yore

  3. #3
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,728
    Blog Entries
    2

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Another passing thought:

    This: "force user = smbuser" would imply that the ownerships of the directories "images" and "images2" and "smbdata/LWW" have owner user=smbuser (and I suppose group=users)
    Leap 42.3 & 15.1 &KDE
    FYIs from the days of yore

  4. #4
    Join Date
    May 2012
    Location
    Finland
    Posts
    2,012

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Tumbleweed switched to SMB3 by default.

    Try defining the client min/max protocol in smb.conf (under [global] )
    Code:
    client min protocol = SMB2 
    client max protocol = SMB3
    Restart smb.
    .: miuku #suse @ irc.freenode.net
    :: miuku@opensuse.org

    .: h​ttps://download.opensuse.org/repositories/home:/Miuku/

  5. #5

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Is smbuser a Linux user on the Tumbleweed server?

    yes, it is.


    Security might drop if you do this
    Try this:
    Code:
    security = user
    And then redo this:
    Code:
    smbpasswd -a smbuser
    No luck.

    These are superfluous I hope:
    Code:
    wins server =
    wins support = No
    But just in case they are doing something, make them like this
    Code:
    ##wins server =
    ##wins support = No
    Then reboot Linux and then reboot Win 7.

    No change (these lines are leftovers from years back and can probably be removed safely).

    Check that the daemons are running. I think they are or some things would already be not working, but just check anyway, these comnads.
    Code:
    systemctl status nmb.service
    systemctl status smb.service
    [/QUOTE]

    These are running fine (and samba connections work fine from clients with Tumbleweed).

  6. #6

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Quote Originally Posted by swerdna View Post
    Another passing thought:

    This: "force user = smbuser" would imply that the ownerships of the directories "images" and "images2" and "smbdata/LWW" have owner user=smbuser (and I suppose group=users)
    That is correct, smbuser is the owner of the shared directories.

  7. #7

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Quote Originally Posted by Miuku View Post
    Tumbleweed switched to SMB3 by default.

    Try defining the client min/max protocol in smb.conf (under [global] )
    Code:
    client min protocol = SMB2 
    client max protocol = SMB3
    Restart smb.
    No change. Connection from Windows7 not possible (Invalid password, error 86) and from Dolphin on Tumbleweed effortlessly.

  8. #8
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,728
    Blog Entries
    2

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    I wonder if win 7 has an error. Internet says it's a real issue and fixable, many instances in google search. For example this: http://www.solvusoft.com/en/errors/w...alid-password/

    Do you have another windows computer you could attach to the LAN, to see if that other windows has a problem?
    Leap 42.3 & 15.1 &KDE
    FYIs from the days of yore

  9. #9
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,296
    Blog Entries
    14

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Anything in a logfile? Or in the journal ?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  10. #10

    Default Re: After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

    Quote Originally Posted by Miuku View Post
    Tumbleweed switched to SMB3 by default.

    Try defining the client min/max protocol in smb.conf (under [global] )
    Code:
    client min protocol = SMB2 
    client max protocol = SMB3
    Restart smb.
    Yes, succeeded! This difference with yesterday's no-luck was a reboot of the Windows client.
    Thanks!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •