similar to: Samba 4 AD share: Access denied

Alright, even with that change they cannot access the share. I do not have SELinux on this system to my knowledge. The only change since my initial post was changing SAMDOM in my config to TRUEVINE as was pointed out. I then rebooted the server for good measure. People in the AD group FBC are still debied access to the FBC share and people in the AD administration group are still denied access to

I believe I have found either a bug or something I do not understand. I recently had a file-share issue and the resolution was to set the "others" permissions to 5, read and execute. The problem with this is that once I am in Windows on a workstation, this appears to allow "Everyone", "CREATOR OWNER", and "CREATOR GROUP" access. We normally setup our

On 03/07/15 15:58, Ryan Ashley wrote: > They left a PC on, so I got the info. The info pissed me off, but not > because of the issue. This time it worked flawlessly, but I got the > error from the event log from prior attempts. First, today's results. > > C:\Users\reachfp.KIGM>gpupdate > Updating Policy... > > User Policy update has completed successfully. >

On 03/07/15 15:18, Ryan Ashley wrote: > The only Unix client I can think of would be the Buffalo NAS. It runs > Samba3 and hosts various shares via SMB. DNS is handled by BIND9 on the > Samba4 DC. DNS does work and the domain name resolves to the IP address > of the server. DHCP is also handled on the DC. As for the GPO's, they're > in the correct place as far as I can tell.

Hi, I am having some issues with a new server install in Singapore. Outbound calls work fine. Inbound calls are not picked up by Asterisk. Zaptel 1.2.25 and Asterisk 1.2.28 both built from source. libpri installed wctdm and zaptel load without error Jun 6 23:34:03 fs01 kernel: [211138.372933] Zapata Telephony Interface Registered on major 196 Jun 6 23:34:03 fs01 kernel: [211138.372937]

Rowland, I commented out what you asked me to, no change. # Global parameters [global] workgroup = TRUEVINE realm = TRUEVINE.LAN netbios name = DC01 server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbi$ # idmap_ldb:use rfc2307 = yes # idmap config *:backend = tdb # idmap

OK, I noticed that also, but why does everything return NT_STATUS_INVALID_SID? Even if I run "smbclient -L \\localhost -U adminnamehere" on the DC itself, I get the error. At this point we are looking at erasing every workstation, wiping the DC, and starting from scratch. It has been a week and not even rolling back to 4.4 fixed it. What should my next steps be? I attached the server

On Wed, 26 Oct 2016 17:27:37 -0400 Ryan Ashley via samba <samba at lists.samba.org> wrote: > I guess I should note that it seems like the high SIDs will resolve, > except for 300000. Below is an example. > > root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/ > total 16 > drwxrws---+ 4 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 Policies > drwxrws---+ 2 MEDARTS\reachfp

Hello everyone. I joined this list because I cannot find an answer to my problem. The setup is this: I installed CentOS release 6.5 (Final) minimal version Updated all packages Added the server to the Active Directory domain as a member server using the method described here (using adcli, kerberos and sssd): http://jhrozek.livejournal.com/3581.html It worked, I tested by trying to connect through

Hi, We are having some issues with LDAP authentication. Here is our setup PDC and LDAP(samba classic) = dc01 SambaClassic domain = stdom Member server = fs01 We migrated from TDB to LDAP. The old TDB users are able to login to the domain and access file shares without issues. Any new user created in LDAP is not able to access the shares. When trying to create shared drives for the new users

I have been trying to mount a windows file share so I can use it for remote storage particularly for my Deki Wiki attachments. Anyway, I seem to have a mount established by doing the following. 1. Added following line to /etc/fstab //fs01/wikidata /var/www/dekiwiki/attachments cifs user,uid=500,rw,suid,username=wikisvcacct,password=testpwd,domain=corporate 2. Then ran following command to

Hi, Not sure exactly how I would word the subject line so appologies in advanced. We are trying to accomplish the following scenario: Location 1: PDC: fs01.loc1.example.com IP: 10.0.0.1 Location 2: SDC: fs01.loc2.example.com IP: 10.0.1.1 Clearly when we join the SDC to the PDC there is a naming conflict. The end result would be to have clients at each site resolve the fs01 name to

Hi, Our setup: Samba (classic) DC: cdr-dc01 Samba (classic) member server: cdr-fs01. This is also a file server AD realm: CDR.internal We migrated to AD and came across an issue with accessing shares. The shares in question worked pre-migrated. i.e using a windows machine a user was able to access that share. The share in question was locked down to just that user Post migration, we are able

Am 25.09.2018 um 12:37 schrieb Rowland Penny via samba: > On Tue, 25 Sep 2018 12:08:00 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > >> Am 25.09.2018 um 11:35 schrieb Rowland Penny via samba: >>> On Tue, 25 Sep 2018 11:18:03 +0200 >>> Daniel Jordan via samba <samba at lists.samba.org> wrote: >>> >>>> Am 24.09.2018 um 19:33

Hi, I'm trying to join my Linux file server to an AD domain. I've looked at several different documents describing how to do this, but I still am not able to get everything to work correctly. I am able to join my domain, but I cannot use smbclient to connect to another file server in the domain, nor can I connect to the samba server from my desktop PC. My kerberos tickets seem to be in

Hello, A few weeks ago we started joining some remote servers to our AD domain as member servers. Several times now we have come back to them and found ownership settings missing like the following. [root at franks-dc1 opt]# ll total 72 drwxrws---+ 3 14505 10013 4096 Nov 28 2006 appinstalls drwxrws---+ 2 14505 10010 4096 Aug 3 2004 bldgshrs drwxrwsr-x+ 2 14505 10011 4096 Aug 3 2004

Sorry, but I didn't really know how to word this. I have Univention Corporate server running as AD DC, with a UCS running as a member fileserver. One win10 client has file permission issues after lack of reboot or logout/login in roughly a weeks time. Symptom = can't write to shares even though permissions are correct. Sometimes files are created without honoring default ACL. Could this

Am 25.09.18 um 14:26 schrieb Rowland Penny via samba: > On Tue, 25 Sep 2018 13:12:18 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > >>>>>>>> dc01:~# samba-tool dbcheck --cross-ncs >>>>>>>> Checking 4503 objects >>>>>>>> SID S-1-5-21-3258148492-1502286889-3538134041-1601 for >>>>>>>>

Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own

They left a PC on, so I got the info. The info pissed me off, but not because of the issue. This time it worked flawlessly, but I got the error from the event log from prior attempts. First, today's results. C:\Users\reachfp.KIGM>gpupdate Updating Policy... User Policy update has completed successfully. Computer Policy update has completed successfully. C:\Users\reachfp.KIGM>gpupdate