ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Samba file share and MS A/D NTFS permissions

    IT Discussion
    4
    25
    2.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ObsolesceO
      Obsolesce @pmoncho
      last edited by

      @pmoncho said in Samba file share and MS A/D NTFS permissions:

      Side Note - how do you highlight your lines red with red box?

      You use the key next to your #1 key, a ` at each end when using it in a sentence.

      Or use three in a row a line before and after for a chunk of code.

      pmonchoP 1 Reply Last reply Reply Quote 0
      • pmonchoP
        pmoncho @Obsolesce
        last edited by

        @obsolesce said in Samba file share and MS A/D NTFS permissions:

        @pmoncho said in Samba file share and MS A/D NTFS permissions:

        @obsolesce said in Samba file share and MS A/D NTFS permissions:

        @pmoncho said in Samba file share and MS A/D NTFS permissions:

        @obsolesce said in Samba file share and MS A/D NTFS permissions:

        A few things have changed recently upon doing a new install as of Friday 7/6.

        On 7/6 I started to install Fedora 28 in our production environment only to hit a snag. I could not access the Samba share via name on any machine. Under normal user, \linuxfax\fax would not resolve but \IP Address showed the Fax folder. No access to share. Admin account was the same with the exception of getting "No RPC server found"

        Following items no longer worked for me;

        chown [email protected]:"domain [email protected]" /share/fax

        In smb.conf file - valid users = @"[email protected]"

        I had to now use:

        chown [email protected]:"Domain.com\domain admins" /share/fax

        In smb.conf file - valid users = @"Domain.com\faxuser"

        Sounds like something is off because you would use that format for trusted domains, not your domain. For example:

        valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"

        Where the first one is your domain, and the second is a different but trusted domain.

        That was the weird part when I kept messing with the "valid users" section.

        "valid users = @"Domain Users"" - wouldn't work so I kept to your documentation.

        I will change it back and see what happens.

        Side Note - how do you highlight your lines red with red box?

        I actually misread what you wrote.

        So @"Domain Users" works, but @"Domain [email protected]" does not work?

        I could not get @"Domain Users" to work (original smb.conf file) so I stuck to @"Domain [email protected]" .

        The issue as of the 7/6/18 Fedora/Samba/Winbind update is @"Domain [email protected]" no longer works and I now use valid users = @"Domain.com\Domain Users"

        ObsolesceO 1 Reply Last reply Reply Quote 0
        • pmonchoP
          pmoncho @Obsolesce
          last edited by

          @obsolesce said in Samba file share and MS A/D NTFS permissions:

          @pmoncho said in Samba file share and MS A/D NTFS permissions:

          Side Note - how do you highlight your lines red with red box?

          You use the key next to your #1 key, a ` at each end when using it in a sentence.

          Or use three in a row a line before and after for a chunk of code.

          I figured it out when quoting your last reply. On all my other replies I did not notice the ` in there. Thanks.

          1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce @pmoncho
            last edited by

            @pmoncho said in Samba file share and MS A/D NTFS permissions:

            @obsolesce said in Samba file share and MS A/D NTFS permissions:

            @pmoncho said in Samba file share and MS A/D NTFS permissions:

            @obsolesce said in Samba file share and MS A/D NTFS permissions:

            @pmoncho said in Samba file share and MS A/D NTFS permissions:

            @obsolesce said in Samba file share and MS A/D NTFS permissions:

            A few things have changed recently upon doing a new install as of Friday 7/6.

            On 7/6 I started to install Fedora 28 in our production environment only to hit a snag. I could not access the Samba share via name on any machine. Under normal user, \linuxfax\fax would not resolve but \IP Address showed the Fax folder. No access to share. Admin account was the same with the exception of getting "No RPC server found"

            Following items no longer worked for me;

            chown [email protected]:"domain [email protected]" /share/fax

            In smb.conf file - valid users = @"[email protected]"

            I had to now use:

            chown [email protected]:"Domain.com\domain admins" /share/fax

            In smb.conf file - valid users = @"Domain.com\faxuser"

            Sounds like something is off because you would use that format for trusted domains, not your domain. For example:

            valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"

            Where the first one is your domain, and the second is a different but trusted domain.

            That was the weird part when I kept messing with the "valid users" section.

            "valid users = @"Domain Users"" - wouldn't work so I kept to your documentation.

            I will change it back and see what happens.

            Side Note - how do you highlight your lines red with red box?

            I actually misread what you wrote.

            So @"Domain Users" works, but @"Domain [email protected]" does not work?

            I could not get @"Domain Users" to work (original smb.conf file) so I stuck to @"Domain [email protected]" .

            The issue as of the 7/6/18 Fedora/Samba/Winbind update is @"Domain [email protected]" no longer works and I now use valid users = @"Domain.com\Domain Users"

            Hmm, not sure what the problem is because I have one running 4.16.9-300.fc28.x86_64 (Fedora 28) that's fully up to date, and it's smb.conf is using the format:

            valid users = @"domain [email protected]"
            admin users = @"domain [email protected]"
            

            Where "domain admins" is a user or group.

            Though, it hasn't been rebooted lately.

            pmonchoP 1 Reply Last reply Reply Quote 0
            • pmonchoP
              pmoncho @Obsolesce
              last edited by

              @obsolesce said in Samba file share and MS A/D NTFS permissions:

              @pmoncho said in Samba file share and MS A/D NTFS permissions:

              @obsolesce said in Samba file share and MS A/D NTFS permissions:

              @pmoncho said in Samba file share and MS A/D NTFS permissions:

              @obsolesce said in Samba file share and MS A/D NTFS permissions:

              @pmoncho said in Samba file share and MS A/D NTFS permissions:

              @obsolesce said in Samba file share and MS A/D NTFS permissions:

              A few things have changed recently upon doing a new install as of Friday 7/6.

              On 7/6 I started to install Fedora 28 in our production environment only to hit a snag. I could not access the Samba share via name on any machine. Under normal user, \linuxfax\fax would not resolve but \IP Address showed the Fax folder. No access to share. Admin account was the same with the exception of getting "No RPC server found"

              Following items no longer worked for me;

              chown [email protected]:"domain [email protected]" /share/fax

              In smb.conf file - valid users = @"[email protected]"

              I had to now use:

              chown [email protected]:"Domain.com\domain admins" /share/fax

              In smb.conf file - valid users = @"Domain.com\faxuser"

              Sounds like something is off because you would use that format for trusted domains, not your domain. For example:

              valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"

              Where the first one is your domain, and the second is a different but trusted domain.

              That was the weird part when I kept messing with the "valid users" section.

              "valid users = @"Domain Users"" - wouldn't work so I kept to your documentation.

              I will change it back and see what happens.

              Side Note - how do you highlight your lines red with red box?

              I actually misread what you wrote.

              So @"Domain Users" works, but @"Domain [email protected]" does not work?

              I could not get @"Domain Users" to work (original smb.conf file) so I stuck to @"Domain [email protected]" .

              The issue as of the 7/6/18 Fedora/Samba/Winbind update is @"Domain [email protected]" no longer works and I now use valid users = @"Domain.com\Domain Users"

              Hmm, not sure what the problem is because I have one running 4.16.9-300.fc28.x86_64 (Fedora 28) that's fully up to date, and it's smb.conf is using the format:

              valid users = @"domain [email protected]"
              admin users = @"domain [email protected]"
              

              Where "domain admins" is a user or group.

              Though, it hasn't been rebooted lately.

              Hmmm... I'm on 4.17.3-200.fc28.X86_64

              Would that be a kernel issue or possible Samba or Winbind? That is the part I cannot figure out. Where the change was the issue.

              I am about to update my old Fedora 4.16 to newest and see if all still works.

              ObsolesceO 1 Reply Last reply Reply Quote 0
              • ObsolesceO
                Obsolesce @pmoncho
                last edited by

                @pmoncho said in Samba file share and MS A/D NTFS permissions:

                @obsolesce said in Samba file share and MS A/D NTFS permissions:

                @pmoncho said in Samba file share and MS A/D NTFS permissions:

                @obsolesce said in Samba file share and MS A/D NTFS permissions:

                @pmoncho said in Samba file share and MS A/D NTFS permissions:

                @obsolesce said in Samba file share and MS A/D NTFS permissions:

                @pmoncho said in Samba file share and MS A/D NTFS permissions:

                @obsolesce said in Samba file share and MS A/D NTFS permissions:

                A few things have changed recently upon doing a new install as of Friday 7/6.

                On 7/6 I started to install Fedora 28 in our production environment only to hit a snag. I could not access the Samba share via name on any machine. Under normal user, \linuxfax\fax would not resolve but \IP Address showed the Fax folder. No access to share. Admin account was the same with the exception of getting "No RPC server found"

                Following items no longer worked for me;

                chown [email protected]:"domain [email protected]" /share/fax

                In smb.conf file - valid users = @"[email protected]"

                I had to now use:

                chown [email protected]:"Domain.com\domain admins" /share/fax

                In smb.conf file - valid users = @"Domain.com\faxuser"

                Sounds like something is off because you would use that format for trusted domains, not your domain. For example:

                valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"

                Where the first one is your domain, and the second is a different but trusted domain.

                That was the weird part when I kept messing with the "valid users" section.

                "valid users = @"Domain Users"" - wouldn't work so I kept to your documentation.

                I will change it back and see what happens.

                Side Note - how do you highlight your lines red with red box?

                I actually misread what you wrote.

                So @"Domain Users" works, but @"Domain [email protected]" does not work?

                I could not get @"Domain Users" to work (original smb.conf file) so I stuck to @"Domain [email protected]" .

                The issue as of the 7/6/18 Fedora/Samba/Winbind update is @"Domain [email protected]" no longer works and I now use valid users = @"Domain.com\Domain Users"

                Hmm, not sure what the problem is because I have one running 4.16.9-300.fc28.x86_64 (Fedora 28) that's fully up to date, and it's smb.conf is using the format:

                valid users = @"domain [email protected]"
                admin users = @"domain [email protected]"
                

                Where "domain admins" is a user or group.

                Though, it hasn't been rebooted lately.

                Hmmm... I'm on 4.17.3-200.fc28.X86_64

                Would that be a kernel issue or possible Samba or Winbind? That is the part I cannot figure out. Where the change was the issue.

                I am about to update my old Fedora 4.16 to newest and see if all still works.

                What versions of samba and winbind are you using?

                1 Reply Last reply Reply Quote 0
                • pmonchoP
                  pmoncho
                  last edited by

                  Using Samba-4.8.3-1.fc28.src.rpm and Samba-winbind-4.8.3-1.fc28.src.rpm

                  ObsolesceO 1 Reply Last reply Reply Quote 0
                  • ObsolesceO
                    Obsolesce @pmoncho
                    last edited by

                    @pmoncho said in Samba file share and MS A/D NTFS permissions:

                    Using Samba-4.8.3-1.fc28.src.rpm and Samba-winbind-4.8.3-1.fc28.src.rpm

                    same

                    1 Reply Last reply Reply Quote 0
                    • ObsolesceO
                      Obsolesce
                      last edited by

                      What file system?

                      pmonchoP 1 Reply Last reply Reply Quote 0
                      • pmonchoP
                        pmoncho @Obsolesce
                        last edited by

                        @obsolesce
                        XFS -

                        I use your document minus Hyper-V, DHCP and automatic updates (I don't install those packages). I differ by creating a separate 5 Gib XFS partition /myshare during setup along with the different info in smb.conf file.

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post