similar to: Samba 4 Bind DNS on CentOS 7

Hi Brady, I realise that but the only named.conf to be found on the system is my newly created /etc/named.conf. Either something screwed up when installing the Sernet RPMs, which is really pretty unlikely given that everything else is working, or the file was not included in the package. regards, John On 21/08/15 10:16, Brady, Mike wrote: > On 2015-08-21 11:18, John Gardeniers wrote:

On 2015-08-21 14:11, Brady, Mike wrote: > On 2015-08-21 12:52, John Gardeniers wrote: >> Hi Brady, >> >> I realise that but the only named.conf to be found on the system is my >> newly created /etc/named.conf. Either something screwed up when >> installing the Sernet RPMs, which is really pretty unlikely given that >> everything else is working, or the file

On 2015-08-21 16:30, John Gardeniers wrote: > Hi Mike, > > I wonder if I'm missing the file because I only did a classicupgrade, > rather than a provision and perhaps then the file(s) is/are not > created. > > regards, > John > > > On 21/08/15 13:45, Brady, Mike wrote: >> On 2015-08-21 14:11, Brady, Mike wrote: >>> On 2015-08-21 12:52, John

Hi Mike, I wonder if I'm missing the file because I only did a classicupgrade, rather than a provision and perhaps then the file(s) is/are not created. regards, John On 21/08/15 13:45, Brady, Mike wrote: > On 2015-08-21 14:11, Brady, Mike wrote: >> On 2015-08-21 12:52, John Gardeniers wrote: >>> Hi Brady, >>> >>> I realise that but the only named.conf

On 2015-08-21 12:52, John Gardeniers wrote: > Hi Brady, > > I realise that but the only named.conf to be found on the system is my > newly created /etc/named.conf. Either something screwed up when > installing the Sernet RPMs, which is really pretty unlikely given that > everything else is working, or the file was not included in the > package. > > regards, > John

On 2015-08-21 18:24, John Gardeniers wrote: > Hi Mike, > > I originally installed using the built-in DNS. Then, after finding it > missing most features, I installed Bind and, lacking the named.con, > tried it including likely sounding files from the Samba setup > directory (OK, I was getting desperate). I then ran "samba_upgradedns > --dns-backend=BIND9_DLZ" and

We're upgrading (Sernet) Samba 4.2 to 4.4. As recommended on this page: https://wiki.samba.org/index.php/Updating_Samba, I have upgraded one of out 2 DCs, the one that does not have any FSMO roles. We will spend the next week making sure everything works as expected. So far, so good. One thing I'm not clear on is whether I should move the FSMO roles to the upgraded DC before upgrading

We're using the Sernet Samba v4.2.4 with internal DNS and I can't find the DNS logs. Where does the Samba 4 internal DNS log queries? Thanks. regards, John

On 11/4/2015 4:13 PM, John Gardeniers wrote: > Nobody? Surely somebody knows where Samba 4 logs its DNS queries, or > was this was a huge oversight and the internal DNS doesn't get logged > at all, as appears to be suggested by my utter failure to locate such > logs. > > On 28/10/15 14:28, John Gardeniers wrote: >> We're using the Sernet Samba v4.2.4 with

no DNS server on that planet logs normal queries just because there si not enough disk space in most setups, there is not benefit log anything except erros and warnings for normal operations what is the problem you like to solve and if there is no problem why do you want logging normal operations? in other words: what do you try to solve except https://wiki.samba.org/index.php/DNS Am

Hi Andrew, I don't understand why 2 systems running the exact same version of Samba have different behaviour. Is this an option I can disable? regards, John On 19/04/16 11:29, Andrew Bartlett wrote: > On Tue, 2016-04-19 at 10:29 +1000, John Gardeniers wrote: >> I'm setting up a test domain in order to try out Sudoers LDAP and >> have >> run into a problem that has

On 11/5/2015 10:30 AM, Rowland Penny wrote: > On 05/11/15 15:18, James wrote: >> On 11/4/2015 4:13 PM, John Gardeniers wrote: >>> Nobody? Surely somebody knows where Samba 4 logs its DNS queries, or >>> was this was a huge oversight and the internal DNS doesn't get >>> logged at all, as appears to be suggested by my utter failure to >>> locate

Probably a ld issue. It might have not run in the rpm's post script. Do a ldd /usr/lib64/samba/libsmbregistry-samba4.so /usr/lib64/samba/vfs/acl_xattr.so and check if either are reporting missing dependencies. Em 07/02/2017 21:25, John Gardeniers via samba escreveu: > This is really weird. The error below occurred for about 10 minutes after the > post-update reboot and then went

I've just done a yum update and a reboot on one of our CentOS 7 DCs, which has taken Samba from sernet-samba-4.5.1-6 to sernet-samba-4.5.5-13. I now notice that the Samba log files contain errors since the update. The error message is: "../lib/util/modules.c:48(load_module) Error loading module '/usr/lib64/samba/vfs/acl_xattr.so': /usr/lib64/samba/libsmbregistry-samba4.so:

Hi Jeremy, No, I don't mean "deadtime". I mean auto disconnect. Specifically, the command "net config server /autodisconnect:-1" was run on each client machine. If deadtime is a server configuration item perhaps you could point me in the direction of some documentation where that is covered. The documentation for smb.conf is, to put it very mildly, incomplete.

I am seeing the following messages logged every 20 min on a Centos 5.5 Samba 3.5.7 (SerNet RPMs) PDC. wins server = yes is set and the 172.17.1.50 address is the address of the PDC. From a Windows client perspective the the domain is functioning as expected. There is a Samba BDC and mulitple Win2008 R2 member servers in the domain. Are they anything to be concerned about? [2011/03/11

Following the instructions here: https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO In that page there is a link to using Bind as your DNS server, which links to: https://wiki.samba.org/index.php/DNS_Backend_BIND On that page, it instructs you to populate the DNS server with the command: /usr/local/samba/sbin/samba_dnsupdate --verbose --all-names Without the "interfaces" and the

Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing problems using Remote Desktop from Windows boxes. The rather useless and completely misleading error message states: "The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the

Hi Rowland, Perhaps I misled you with my wording. Each user has just one email address, which was not migrated across. From where I'm sitting that looks like a very serious bug. regards, John On 31/08/15 19:07, Rowland Penny wrote: > On 31/08/15 07:27, John Gardeniers wrote: >> I've been running through a bunch of tests after migrating from >> Samba > 3 to Samba 4

Hello, is it possible to configure Samba that only check User+Password is OK on a Active Directory Server ´s ( No Domain Join of the Samba Server) ? Thanks Dennis