similar to: NETLOGON failure

Hi Rowland, > Are you sure this is a Samba problem, I only ask this because a quick > google brings up lots of results like this: > > https://support.microsoft.com/en-us/kb/2459530 > > Where it is very clearly a windows problem, so much so, that there is a > hotfix available. Reading that page, it seems like exactly the issue we're seeing: both Netlogon event ID 5719

On 22/11/15 13:11, Viktor Trojanovic wrote: > Hi list, > > Checking the Windows event logs, I see that my clients regularly > complain a netlogon failure: > > Event 5719, NETLOGON > This computer was not able to set up a secure session with a domain > controller in domain SAMDOM due to the following: > There are currently no logon servers available to service the logon

On 25.01.2016 14:13, Viktor Trojanovic wrote: > Hi Ole, > > Unless you want to add functionality that is new since 1511, I don't > think that's necessary. I have already added a Win10 machine to a domain, where only Win7 clients were joined before that. I have managed this domain from Win7 only, so far. Therefore I believe that e.g. the Windows Update policy is not fit for

Viktor, thanks again! Now that I did this (added the Win10 1511 ADMX files to the central store), I probably will have to recreate the policies that will be applied to Win10 machines, right? Ole On 21.01.2016 17:16, Viktor Trojanovic wrote: > Hi Ole, > > I've been using Samba with Win10 clients for a while now, so I'm happy > to share some of my findings. > > See

Hi list, This might or might not be a Samba related post. Feel free to ignore it in case it is too far off-topic My current understanding is that ... a) I need those new templates in order to fully integrate Win10 clients in an AD domain (i.e. with compatible policies). b) I can only modify policies based on Win10 admx files from Win10 machines (i.e. with the RSAT tools for Win10). Are there

Hi Viktor, I didn't go through all the conversations and I'm not sure if this will > be of any help, I just wanted to inform that I've been using mapped > drives with Windows 10 for ages and never had the problems you > described. I also never added or changed the "smb encrypt" option. My > Samba file server (AD member) was set up pretty much the way as is >

I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it and just noticed that the clients are not synchronizing time with the server. I'm not sure why not. My setup is a bit special in that the DC is running inside a (privileged) linux container. For that reason, it's not possible or necessary for the container to correct the system clock, this is done on the

On 16.11.2019 23:37, Sonic wrote: > On Sat, Nov 16, 2019 at 10:34 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I think you may be confusing privileged with unprivileged containers, >> what you describe is perfectly possible with a privileged container but >> would be a bit more complicated to set up with an unprivileged one >> (since the user id's in the

On 16.11.2019 15:17, Sonic wrote: > On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba > <samba at lists.samba.org> wrote: >> I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it >> and just noticed that the clients are not synchronizing time with the >> server. I'm not sure why not. >> >> My setup is a bit special in

Let me guess. You accessing your server like : \\servername\netlogon of \\servername\sysvol Well thats protected by windows these these days. Try with \\servername.domain.tld\netlogon or \\servername.domain.tld\sysvol Does that work? Yes, There is a whole chaper of this on the list somewhere.. Best is to read howto override this. https://adsecurity.org/?p=1405 and for you

I was experiencing problems with Group Policy Objects. The Windows Event Viewer spits out so many different errors, most of them less than helpful, so Iwas seeking help here with some of those messages. In the end, and after many hours and even days of researching this problem, I seem to have pin-pointed the main issue to some simple permission irregularities that I don't know how to

On 27.10.2015 11:17, Rowland Penny wrote: > On 27/10/15 09:34, Viktor Trojanovic wrote: >> >> >> On 27.10.2015 09:05, Rowland Penny wrote: >>> On 26/10/15 22:35, Viktor Trojanovic wrote: >>>> >>>> >>>> On 26.10.2015 23:03, Rowland Penny wrote: >>>>> On 26/10/15 21:38, Viktor Trojanovic wrote: >>>>>>

On 27.10.2015 09:05, Rowland Penny wrote: > On 26/10/15 22:35, Viktor Trojanovic wrote: >> >> >> On 26.10.2015 23:03, Rowland Penny wrote: >>> On 26/10/15 21:38, Viktor Trojanovic wrote: >>>> I joined a Samba AD member server (file server) to a Samba AD DC. >>>> This seems to have worked. However, if I try to access the file >>>>

On 21.01.2016 15:51, James wrote: > On 1/21/2016 9:39 AM, Ole Traupe wrote: >> Hi list, >> >> This might or might not be a Samba related post. Feel free to ignore >> it in case it is too far off-topic >> >> My current understanding is that ... >> a) I need those new templates in order to fully integrate Win10 >> clients in an AD domain (i.e.

Here are my (little) view regarding shares accesses. I write that to clarify things. And it could really be of-topic as Louis seems to have gave solution. There are 2 levels of authorisation for accessing shares: the share level and FS level. For Sysvol I would keep everyone or replace it by "authenticated users" in paranoid mode as the latter refuse non-authenticated users. They are

I’m currently trying to install a new (primary) AD DC in a Linux container. It seems to me that being in a container, the DC is easier to maintain and backup than on bare metal, and I prefer a container over a VM for performance reasons. If the container setup will prove to be too much of hassle, I’ll switch to a VM, though. The first issue I’m facing is time synchronization. An container cannot

On 27.10.2015 12:38, Rowland Penny wrote: > See inline comments: > > On 27/10/15 11:17, Viktor Trojanovic wrote: >> >> >> On 27.10.2015 11:17, Rowland Penny wrote: >>> On 27/10/15 09:34, Viktor Trojanovic wrote: >>>> >>>> >>>> On 27.10.2015 09:05, Rowland Penny wrote: >>>>> On 26/10/15 22:35, Viktor Trojanovic

On 17/11/15 16:57, Viktor Trojanovic wrote: > Hi Mathias, > > Thanks for replying. It seems you're describing the situation on the > AD DC. Computer and user mode access to my DC works fine and without > any issues but I can't access the shares of my *member* server *in > computer mode*. In user mode, it all works just fine. > > Viktor > > On 17.11.2015

On 26.10.2015 23:03, Rowland Penny wrote: > On 26/10/15 21:38, Viktor Trojanovic wrote: >> I joined a Samba AD member server (file server) to a Samba AD DC. >> This seems to have worked. However, if I try to access the file >> server from the domain administrator account on a Windows client, I >> am asked to provide authorization details. Since I have no other

On 6/19/2017 9:12 AM, Viktor Trojanovic via samba wrote: > On 19 June 2017 at 14:56, Rowland Penny via samba <samba at lists.samba.org> > wrote: > >> On Mon, 19 Jun 2017 14:46:34 +0200 >> Viktor Trojanovic <viktor at troja.ch> wrote: >> >>> On 19 June 2017 at 14:20, lingpanda101 via samba >>> <samba at lists.samba.org> wrote: