similar to: Problem with Samba 4.0.4 to 4.1.19 update

Good morning Rowland. Today there are 2 servers with Samba 4.1.19 1) Samba 4.1.19 compiled used for the control domain (AD) 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain join" to use the Squid authenticating via NTLM. Before I was as follows: 1) Samba 4.0.4 compiled AD 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain

good day Ali Bendriss, I followed exactly this tutorial to update the samba. Thank you, everyone I'll be honest as I have full knowledge about the Samba 4 will redo the structure thus have more work more on the other hand I'm sure I will not make a mistake that can generate me more trouble. Regards, Gabriel Franca > Em 14/08/2015, à(s) 09:39, Ali Bendriss <ali.bendriss at

Hello Rowland Talking to users at that time discovered the following: They remove the machine network cable, put the User and Password them the domain, after the windows open the desktop they connect the network cable back in the machine and get to work. If you do this procedure is giving User and wrong password! On the issue of time the 2 DC's station using ntp. I stopped the samba

On 08/13/2015 01:46 PM, Gabriel Franca wrote: > Good morning friends, > > I have the following structure: > > Centos 6.6 > > 1) AD samba using .tgz package > > 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. > > Issues: > > 1) after the update I get the

On 13/08/15 12:46, Gabriel Franca wrote: > Good morning friends, > > I have the following structure: > > Centos 6.6 > > 1) AD samba using .tgz package > > 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. > > Issues: > > 1) after the update I get the

On 13/08/15 13:12, Gabriel Franca wrote: > Good morning Rowland. > > Today there are 2 servers with Samba 4.1.19 > > 1) Samba 4.1.19 compiled used for the control domain (AD) > 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain join" to use the Squid authenticating via NTLM. > > Before I was as follows: > > 1) Samba 4.0.4 compiled AD

On 13/08/15 13:58, Gabriel Franca wrote: > Hello Rowland > > Talking to users at that time discovered the following: > > They remove the machine network cable, put the User and Password them the domain, after the windows open the desktop they connect the network cable back in the machine and get to work. > > If you do this procedure is giving User and wrong password! I am not

Am 02.07.19 um 16:24 schrieb Stefan G. Weichinger via samba: > Am 02.07.19 um 16:09 schrieb Stefan G. Weichinger via samba: >> >> I get problems with group policies not applied ... seems an older >> problem surfacing now. >> >> Before I debug at current level I consider upgrading the 2 DCs from >> 4.8.12 (Debian Stretch) to 4.9.9 >> >> Anything

I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

Rowland, The domain functioned normally before upgrading. the servers are enabled with NTP and the machines should take their time. What do you think better to do in this situation? again make the entire structure from scratch? or can save the samba structure 4 att, Gabriel Franca > Em 13/08/2015, à(s) 10:20, Rowland Penny <rowlandpenny241155 at gmail.com> escreveu: > > I

>Hi, please don't use .local, you say that no apple devices will come >near, but what about an iphone ? and what about avahi ? >When you ran configure, you might as well just run it like this: ./configure >All the rest are defaults and you do not really need debug. >You only need to alter /etc/nsswitch.conf (yes that's the one) if you >want/need your users to log into

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 12 juli 2019 10:24 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO infrastructure? -> 4.8.x to 4.9.x > > Am 10.07.19 um 08:40 schrieb Stefan G. Weichinger via samba: > > > more of this: > >

All, I am running samba as an AD on a Debian buster: *ii python-samba 2:4.9.5+dfsg-5+deb10u1 armel Python bindings for Sambaii samba 2:4.9.5+dfsg-5+deb10u1 armel SMB/CIFS file, print, and login server for Unixii samba-common 2:4.9.5+dfsg-5+deb10u1 all common files used by both the Samba server and clientii

I get problems with group policies not applied ... seems an older problem surfacing now. Before I debug at current level I consider upgrading the 2 DCs from 4.8.12 (Debian Stretch) to 4.9.9 Anything specific to consider here?

Thanks, Rowland. I'll give it some thought. At this point, I may even go back to slackware or gentoo. It is a bit much learning all the new system tools (systemd, systemctl, firewalld, NetworkManager, etc.) while moving from a samba standalone configuration to AD/DC, DNS, Kerberos, all for the first time. I'm also considering calling Pantek.com - - - I've had some very good

Hai, ? Just a tip for the people reading the list. ? if you see Failed DNS update - NT_STATUS_IO_TIMEOUT? or messages : ?RPC unavailable if you connect from windows client to the samba AD DC server ? Read this. ? I have a "test' AD DC on a XEN server running and this DC does nothing. 1 pc ( win7) is joined, some dns recored are set, nothing special.. ? today i checked the logs, and

I wanted to follow up to the list in hopes it will help others with similar configuration. Per previous posts -- OS: CentOS 7.153 Samba: Version 4.1.17-SerNet-RedHat-11.el7 Samba provisioned to act as: AD DC following Samba Wiki: Samba AD DC HOWTO Samba Internal DNS daemon deployed. 1. Disable selinux. Unless you have a solid understanding of how to configure it for your environment, please

Hai, ? Im seeing something very strange.? ( Debian wheezy, sernet-samba 4.1.14 ) ? after update-ing my debian servers and restarting them, im see-ing the following on my ADDC2. ? [2015/01/19 11:09:10.422641,? 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) ? ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT ? I?checked the SOA's of the DNS and

I followed the manual and got 3 problems 1. When i start samba i got error: ../dsdb/dns/dns_update.c:249: Failed DNS update - NT_STATUS_IO_TIMEOUT 2. When i join some computer bind9 doesent update the host in DNS. 3. When i start command /usr/local/samba/sbin/samba_dnsupdate --verbose shell sometimes back result sometimes not.'' -- -- Pozdrav Aleksandar