Displaying 7 results from an estimated 7 matches for "589789".
Did you mean:
58789
2020 Oct 05
2
SID security
...t for upgrading to v4.13.0 too soon.
On W10, logged in as administrator, connected to the member server via
FileExplorer, the file permissions (via Properties tab) >> Security (tab >>
Advanced >> shows the following permissions for the \\mbr04\data folder:
Creator Group
S-1-5-21-589789-1426474111-2143966843-500
S-1-5-21-589789-1426474111-2143966843-512
S-1-5-21-589789-1426474111-2143966843-513
Any member of "Domain Users" should be able to access this folder. The
mbr04 server shows this:
root at mbr04:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500
failed to ca...
2020 Oct 05
2
SID security
...ilding the OS, I kept the "old" /srv/samba files. Which in turn kept
the old permission settings. I think (could be wrong) that keeping the old
SID are now different from the new SID's created while rebuilding to
v4.12.6.
To answer your DC question:
root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500
failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND
Could not lookup sid S-1-5-21-589789-1426474111-2143966843-500
root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-512
failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND
Could not lookup sid S-1-5-21-5897...
2020 Oct 05
2
SID security
...Which in turn
> > kept the old permission settings. I think (could be wrong) that
> > keeping the old SID are now different from the new SID's created while
> > rebuilding to v4.12.6.
> >
> > To answer your DC question:
> > root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500
> > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND
> > Could not lookup sid S-1-5-21-589789-1426474111-2143966843-500
> > root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-512
> > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_...
2020 Jun 19
2
Add gidNumber for group
...n admins
SAMDOM\domain users
SAMDOM\domain guests
SAMDOM\domain computers
SAMDOM\domain controllers
SAMDOM\schema admins
SAMDOM\enterprise admins
SAMDOM\group policy creator owners
SAMDOM\read-only domain controllers
SAMDOM\dnsupdateproxy
root at dc01:~# wbinfo -n "Domain Users"
S-1-5-21-589789-1426474111-2143966843-513 SID_DOM_GROUP (2)
I have been troubleshooting to confirm a properly setup AD? DC and
member server.
All previous tests are passing.
Could I have some other issue?
--
Bob Wooden
2020 Jun 19
0
Add gidNumber for group
...> SAMDOM\domain computers
> SAMDOM\domain controllers
> SAMDOM\schema admins
> SAMDOM\enterprise admins
> SAMDOM\group policy creator owners
> SAMDOM\read-only domain controllers
> SAMDOM\dnsupdateproxy
>
> root at dc01:~# wbinfo -n "Domain Users"
> S-1-5-21-589789-1426474111-2143966843-513 SID_DOM_GROUP (2)
>
> I have been troubleshooting to confirm a properly setup AD? DC and
> member server.
>
> All previous tests are passing.
>
> Could I have some other issue?
>
Did you miss this:
if Domain Users does not have a gidNumber, you pr...
2003 Jan 25
0
(no subject)
>Message: 1
>Date: Fri, 24 Jan 2003 18:03:19 +0100
>To: samba@lists.samba.org
>From: Davide Cavaleri <davide.cavaleri@libero.it>
>Subject: [Samba] linux server completely hangs copying files with samba
>
>hi,
>i'm experiencying a strange problem with a mandrake 9.0 machine,
>kernel 2.4.19, samba (different versions, including latest).
>when I copy large
2020 Jun 19
2
Add gidNumber for group
On 6/19/2020 10:00 AM, Rowland penny via samba wrote:
>
> The easiest way is to upgrade to 4.12.x and then use '_*samba-tool
> group addunixattrs*_', otherwise you could use ldbedit or create an
> ldif and use ldbmodify or ldapmodify. Another option would be to use
> something like LAM.
>
> Rowland
Sorry, but, there is what you told me to do in your first email