Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Kubuntu 18.04 LTS and Windows Workgroup

  1. #11
    Join Date
    Aug 2019
    Beans
    21

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    1) I've put the two "auth" lines into smb.conf
    2) I've changed the Netbios name to HPLINUX, and when that made no difference I changed the HOSTS and HOSTNAME files to match, to no avail.

    To reiterate, everything works except the ability to write to the Linux machine, ie I can make it read and I can read/write from the Linux machine to any of my other devices. We're missing something basic and probably with permissions.

    The outputs now are:
    Code:
    al@hplinux:~$ net usershare info --long 
    [Documents]
    path=/home/al/Documents
    comment=
    usershare_acl=Everyone:F,HPLINUX\shares:F,HPLINUX\al:F,
    guest_ok=y
    
    [Downloads]
    path=/home/al/Downloads
    comment=
    usershare_acl=Everyone:R,HPLINUX\shares:F,
    guest_ok=n
    
    info_fn: file /var/lib/samba/usershares/lenovo moved is not a well formed usershare file.
    info_fn: Error was Path is not a directory.
    **Note the last folder error is just further testing and unless relevant can be ignored for the purposes of this thread
    Code:
    al@hplinux:~$ testparm -s
    Load smb config files from /etc/samba/smb.conf
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    WARNING: The "syslog" option is deprecated
    Processing section "[printers]"
    Processing section "[print$]"
    Processing section "[public]"
    Processing section "[share1]"
    Processing section "[SECURED]"
    Loaded services file OK.
    Server role: ROLE_STANDALONE
    
    # Global parameters
    [global]
        client max protocol = NT1
        dns proxy = No
        lanman auth = Yes
        log file = /var/log/samba/log.%m
        map to guest = Bad User
        max log size = 1000
        ntlm auth = ntlmv1-permitted
        pam password change = Yes
        panic action = /usr/share/samba/panic-action %d
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        passwd program = /usr/bin/passwd %u
        server string = %h server (Samba, Ubuntu)
        syslog = 0
        usershare allow guests = Yes
        workgroup = DATAREVUE
        idmap config * : backend = tdb
    
    
    [printers]
        browseable = No
        comment = All Printers
        create mask = 0700
        path = /var/spool/samba
        printable = Yes
    
    
    [print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers
    
    
    [public]
        comment = Public Share
        force user = nobody
        path = /home/al/Documents
        read only = No
    
    
    [share1]
        comment = A Shared Directory
        force user = nobody
        path = /home/al/Documents
        read only = No
    
    
    [SECURED]
        path = /samba/shares
        read only = No
        valid users = @smbgrp
    ** I'm ending up with too many tests! But each time I amend smb.conf and reset it shows up on the Windows machine.
    Last edited by coffeecat; August 31st, 2019 at 02:08 PM. Reason: added code tags

  2. #12
    Join Date
    Dec 2009
    Beans
    6,255

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    [public]
    comment = Public Share
    force user = nobody
    path = /home/al/Documents
    read only = No
    That makes no sense. That is a share that requires credentials to access but when the remote user passes the correct credentials his identity will change to "nobody". Even if "nobody" had write access to the folder ( which would only happen if you ran chmod 777 /home/al/Documents ) anything saved would be owned by nobody and al wouldn't be able to do anything with it.

    Add this under the workgroup line as I suggested originally:
    Code:
    force user = al
    And change the example share definition to this:
    [public]
    comment = Public Share
    force user = al
    path = /home/al/Documents
    read only = No
    THen restart smbd again.
    Last edited by Morbius1; August 31st, 2019 at 01:59 PM.

  3. #13
    Join Date
    Jun 2006
    Location
    UK
    Beans
    Hidden!
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    @anthonyl2019, I've added BBCode code tags to three of your posts. You'll see that has restored the columnar formatting that was lost by posting it as ordinary text in the bode of the post. The forum software strips out adjacent spaces unless they are enclosed in code tags. When posting terminal output or the contents of config files, please use code tags.

    There's a link in my sig to a guide for using code tags should you need it.

    Thanks.
    Ubuntu 16.04 Desktop Guide - Ubuntu 18.04 Desktop Guide - Forum Guide to BBCode - Using BBCode code tags - IRC #ubuntuforums

    Member: Not Canonical Team

    Please do not PM me about your forum account unless you have been asked to. The correct place to contact an admin about your account is here.

  4. #14
    Join Date
    Aug 2019
    Beans
    21

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    Quote Originally Posted by Morbius1 View Post
    That makes no sense. That is a share that requires credentials to access but when the remote user passes the correct credentials his identity will change to "nobody". Even if "nobody" had write access to the folder ( which would only happen if you ran chmod 777 /home/al/Documents ) anything saved would be owned by nobody and al wouldn't be able to do anything with it.

    Add this under the workgroup line as I suggested originally:
    Code:
    force user = al
    And change the example share definition to this:

    THen restart smbd again.
    Well I'm afraid at this stage a lot of it doesn't make sense to me despite having successfully setup and installed Novell networks (from v2 to v4), Windows NotWorking from (3.x) and my own little LAN at home now I'm retired so I'm at the mercy of what I find on various forums.

    However, thank you very much because I now have read/write access to the Public folder and I'll go through the exercise of tidying up the mess I've created and probably setting my host/hostname back again.

    If I had wanted to have a login to a folder from Windows to Linux what should I now do?

  5. #15
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    14,427
    Distro
    Kubuntu Development Release

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    Adding an entry to /etc/fstab will permanently mount the Windows shares.

    https://wiki.ubuntu.com/MountWindowsSharesPermanently

    You'll need to install the cifs-utils package.
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  6. #16
    Join Date
    Aug 2019
    Beans
    21

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    Quote Originally Posted by SeijiSensei View Post
    Adding an entry to /etc/fstab will permanently mount the Windows shares.

    https://wiki.ubuntu.com/MountWindowsSharesPermanently

    You'll need to install the cifs-utils package.
    Thanks, but that is looking at it the wrong way, I'm trying to see Linux from WIndows not Windows from Linux (which has never been a problem).

    However I will bear that in mind though I'm wary of having too many packages installed.

  7. #17
    Join Date
    Aug 2019
    Beans
    21

    Re: Kubuntu 18.04 LTS and Windows Workgroup

    Quote Originally Posted by anthonyl2019 View Post
    However, thank you very much because I now have read/write access to the Public folder and I'll go through the exercise of tidying up the mess I've created and probably setting my host/hostname back again.

    If I had wanted to have a login to a folder from Windows to Linux what should I now do?
    I now have it all working as I wish though I don't exactly know how, but I will share what bit of knowledge I have:

    1) The Dolphin file manager allows the Properties of a folder to be changed to make it Shareable to Windows. This creates an entry in
    /var/lib/samba/usershares/ for that sharename and Windows 7 can log into that share but XP cannot

    2) I've amended smb.conf, in part with the suggestions from here and in truth I do not know which bits make it work and which bits are redundant so good luck if you are trying it yourself but the result is that I am asked to login and I use my username/smbpassword. The desired folders are NOT shared through the file manager.
    I've cleaned up hosts (simply localhost for ip4) and hostname hplinux

    The key entries as far as I understand are, where 'al' is me as the user:

    Code:
    #31.08.19 try shorter netbios name
    netbios name = hplinux
    
    #31.08.19 from thread
        lanman auth = yes
        ntlm auth = yes
        force user = al
        workgroup = DATAREVUE
        Client Max protocol = NT1
    
    and I've commented out:
    
    #al 3.9.19   passdb backend = tdbsam
    #al 3.9.19  obey pam restrictions = yes
    
    [home]
    comment = al Docs
    path = /home/al/Documents
    force user = al
    read only = No 
    writable = yes
    New folders can be added quite readily and it seems that smb.conf does not need to be restarted for them to take effect, they are there immediate.

    I'll now mark this thread as [SOLVED] and move on to the next steps of my conversion from Windows to Linux. See you on another forum/board/post.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

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