search for: mulple

OS = Ubuntu 18.04 LXD container Samba version = 4.11.12 Repo = Louis' (many thanks) I recently upgraded from 4.10.14->4.10.17->4.11.12 Now the samba-ad-dc service fails with the following upon reboot: --- root at samba:~# systemctl status samba-ad-dc ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)

...ve multiple levels of subprojects that include eachothers' header files (eg. In ffmpeg, avcodec uses avutil etc), and therefore speex doesn't need to include headers from different folders, they are all in the same folder and there is no reason to include them that strange way. If SPEEX had mulple subprojects (like speexdsp, speexutils etc) then to use some speex a programmer would have to add include search path to find speex, but still there is no reason for the speexdsp and speexutil to include each other's headers using <>! I'm not sure how much you care about ms compiler,...

...van Belle via samba <samba at lists.samba.org> wrote: Hai Jonathan, This is/looks like a resolving issue fd61:5ced:6c27:0:216:3eff:fe9b:802a << is this, 'this' server or a remote ? You have mutiple options, but try the most simple one. Take above add it in /etc/hosts ( if mulple dc's might be needed todo that on all DC's.) And if that fixes it, add it as AAAA record to the DNS, ( AND, dont forget the PTR record on the AAAA) Also, i've set samba-ad-dc.service to load like this. systemctl edit samba-ad-dc # /etc/systemd/system/samba-ad-dc.service.d/override...

...pply GPO" > A computer GPO, needs Domain computers with apply GPO AND the users group. > > > I've setup all "problem" shares, due to user NT Authority\SYSTEM problems. > Google for it, you see lots of it in the samba list. > My shares layout that used it. ( on mulple servers ) > DC: Sysvol and Netlogon > Members: users and profiles > Print server: print$ and printers > > So in short, all shares were the "computer$" my access as user system or things like that. > > If you see errors on a computer in the eventlogs with: > Compu...

Hai Jonathan, This is/looks like a resolving issue fd61:5ced:6c27:0:216:3eff:fe9b:802a << is this, 'this' server or a remote ? You have mutiple options, but try the most simple one. Take above add it in /etc/hosts ( if mulple dc's might be needed todo that on all DC's.) And if that fixes it, add it as AAAA record to the DNS, ( AND, dont forget the PTR record on the AAAA) Also, i've set samba-ad-dc.service to load like this. systemctl edit samba-ad-dc # /etc/systemd/system/samba-ad-dc.service.d/override...

ok, do the following. set ignore systemacl to yes on sysvol and netlogon. login as dom\administrator computer manager, connect to dc. share sysvol, goto share security, reset to defalts. same for folder. goto gpo manager, klik on every gpo object, if one has wrong acl, you get a message to reset it, thats ok. now never samba-tool sysvol reset if you do, you might need to set share/file

...r is fine, and needs "apply GPO" A computer GPO, needs Domain computers with apply GPO AND the users group. I've setup all "problem" shares, due to user NT Authority\SYSTEM problems. Google for it, you see lots of it in the samba list. My shares layout that used it. ( on mulple servers ) DC: Sysvol and Netlogon Members: users and profiles Print server: print$ and printers So in short, all shares were the "computer$" my access as user system or things like that. If you see errors on a computer in the eventlogs with: Computer$ can access .... Bla bla.... On...

...user is fine, and needs "apply GPO" A computer GPO, needs Domain computers with apply GPO AND the users group. I've setup all "problem" shares, due to user NT Authority\SYSTEM problems. Google for it, you see lots of it in the samba list. My shares layout that used it. ( on mulple servers ) DC: Sysvol and Netlogon Members: users and profiles Print server: print$ and printers So in short, all shares were the "computer$" my access as user system or things like that. If you see errors on a computer in the eventlogs with: Computer$ can access .... Bla bla.... On GPO.in...

...a.org> wrote: > > Hai Jonathan, > > This is/looks like a resolving issue > > fd61:5ced:6c27:0:216:3eff:fe9b:802a << is this, 'this' server or a remote > ? > > You have mutiple options, but try the most simple one. > Take above add it in /etc/hosts ( if mulple dc's might be needed todo that > on all DC's.) > And if that fixes it, add it as AAAA record to the DNS, ( AND, dont forget > the PTR record on the AAAA) > > Also, i've set samba-ad-dc.service to load like this. > > systemctl edit samba-ad-dc > > # /etc/system...

I'm just curious, who and why came up with that strange way to write includes: #ifdef _BUILD_SPEEX # include "speex_types.h" #else # include <speex/speex_types.h> #endif I personally consider it a bug. If I use speex then obviously I should not have _BUILD_SPEEX defined. The broken behavior happens in this simple scenario: 1) I check out latest git version to ./src/speex 2)