similar to: FreeBSD-11 Samba44 DNS

Displaying 20 results from an estimated 10000 matches similar to: "FreeBSD-11 Samba44 DNS"

2017 Feb 08
3
ntp and samba43 on FreeBSD-103.
On Tue, February 7, 2017 14:29, Alnis Morics wrote: > May I ask an off-topic question? > > James, does saying "samba43" mean you installed this FreeBSD port or > package? Which is known to crash during provisioning as DC. Did you > find the solution to that issue? > Samba43 was installed on FreeBSD-10.3 as a binary package using the pkg utility. Other than ignorance I
2016 Sep 02
4
Segmentation fault in samba_upgradedns - Samba 4.4.5
On Fri, 2 Sep 2016 13:03:05 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 2 Sep 2016 12:41:47 +0100 > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > On 2 September 2016 at 12:21, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Fri, 2 Sep 2016 11:51:02 +0100
2016 Sep 02
2
Segmentation fault in samba_upgradedns - Samba 4.4.5
On 2 September 2016 at 12:21, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Fri, 2 Sep 2016 11:51:02 +0100 > Cameron Murdoch <cam at macaroon.net> wrote: > > > On 2 September 2016 at 09:53, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Thu, 1 Sep 2016 14:12:21 +0100 > > >
2016 Sep 02
2
Segmentation fault in samba_upgradedns - Samba 4.4.5
On Thu, 1 Sep 2016 14:12:21 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > Trying to understand why you are getting the segfault, I set up freebsd 11.0rc2 in a VM and then installed samba44, I now know where Gentoo gets its ideas from :) After freebsd built everything in the chain of required packages, it finally built Samba, I did notice two things, one it built
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
Hi, I continue setting up my FreeBSD 11.0 machine with Samba 4.4.9 built from sources. (Actually, OS type and Samba version don't matter so much, as I have the same problem with Debian Jessie and Samba 4.5.5) I followed the Wiki very close. Some details from provisioning: ... Realm [RW.LAN]: Domain [RW]: Server Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL,
2017 Jan 29
5
"net rpc" commands don’t work on Samba AD DC
Hello, I built Samba 4.5.4 on a FreeBSD 11.0 machine, and I’m trying to set up an AD DC with a file share. So I did this: - enabled ACLs on my UFS2 filesystem (before compilation) - successfully provisioned (rfc2307, internal DNS) - tested local shares, DNS, Kerberos - adjusted NTPd as suggested in Wiki - added this to the global section of smb.conf: template shell = /usr/sbin/nologin template
2017 Feb 09
1
FreeBSD-11 Samba44 DNS
I touched the two missing files /var/db/samba4/private/dns_update_list /var/db/samba4/private/spn_update_list And restarted the Samba44 service. This is what I see now: [2017/02/09 15:48:47.507874, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.4.8 started. Copyright Andrew Tridgell and the Samba Team 1992-2016 [2017/02/09 15:48:47.922389, 0]
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 16:36, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 16:16:28 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> >> >> On 02/06/2017 15:43, Rowland Penny via samba wrote: >>> On Mon, 6 Feb 2017 14:47:21 +0200 >>> Alnis Morics via samba <samba at lists.samba.org> wrote: >>> >>>> I
2017 Feb 06
3
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 15:43, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 14:47:21 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> I see. But I don't necessarily need homedirs and hence PAM configured >> just to log in from Windows and access a file share from there, do I? >> Or even just to log in on Windows to the domain. >>
2017 Feb 08
0
ntp and samba43 on FreeBSD-103.
On Wed, February 8, 2017 10:40, James B. Byrne wrote: > > Samba43 was installed on FreeBSD-10.3 as a binary package using the > pkg utility. Other than ignorance I had no problems with provisioning > a Domain with it. On the other hand Samba44 could not be successfully > provisioned at the time I was setting Samba up which is why we went > with Samba43. > > The ports
2017 Mar 05
1
Samba-4.6.0rc4 on FreeBSD
Hi, I just tried Samba-4.6.0rc4 on FreeBSD 11.0-RELEASE-p8 to see if there's still a problem with "net rpc" commands but it crashed already at provision: # samba-tool domain provision --use-rfc2307 --interactive Realm [RW.LAN]: Domain [RW]: erver Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: DNS
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 13:36, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 12:57:19 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> >> >> On 02/06/2017 11:48, Rowland Penny via samba wrote: >>> On Mon, 6 Feb 2017 11:11:09 +0200 >>> Alnis Morics via samba <samba at lists.samba.org> wrote: >>> >>>>
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
Thank you, Rowland, for the reply. On 02/06/2017 10:44, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 10:07:18 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I continue setting up my FreeBSD 11.0 machine with Samba 4.4.9 built >> from sources. (Actually, OS type and Samba version don't matter so >> much, as I
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 11:48, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 11:11:09 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> Thank you, Rowland, for the reply. >> > >> And the nss tests as per Wiki seem to pass: >> > >> >> # getent passwd Administrator >>
2016 Sep 02
0
Segmentation fault in samba_upgradedns - Samba 4.4.5
On 2 September 2016 at 13:19, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Fri, 2 Sep 2016 13:03:05 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Fri, 2 Sep 2016 12:41:47 +0100 > > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > > > On 2 September 2016 at 12:21, Rowland Penny
2017 Feb 09
1
FreeBSD-11 Samba44 DNS
I have provisioned an AD-DC using Samba-v.4.4 on a FreeBSD-11.0 host. For some reason this DC is not listening on port 53. The configuration file has this entry: server role = active directory domain controller On our current AD-DC which is a Samba-4.3 service Samba listens on 53. But it does not do so for the 4.4 version. Both services were provisioned in much the same fashion. Did
2017 Feb 07
5
ntp and samba43 on FreeBSD-103.
Recently we have been having a lot of trouble with time synchronisation between our samba DC and the domain clients. We are not sure what started this issue since the Samba domain went live on October 11, 2016 and the issues only began to surface this past January but at some point the time on the clients and the DC diverged enough that we began to get strange network errors. Once we figured out
2017 Feb 09
1
FreeBSD-11 Samba44 DNS
Well, I have discovered the proximate cause of why samba-4.4 is not listening on 53. It is because the DNS service dies due to missing files in /var/db/samba4/private/. Specifically dns_update_list. There are a number of missing files in the samba error logs. No such file or directory: '/var/db/samba4/private/spn_update_list' No such file or directory:
2016 Sep 02
0
Segmentation fault in samba_upgradedns - Samba 4.4.5
On Fri, 2 Sep 2016 12:41:47 +0100 Cameron Murdoch via samba <samba at lists.samba.org> wrote: > On 2 September 2016 at 12:21, Rowland Penny via samba > <samba at lists.samba.org > > wrote: > > > On Fri, 2 Sep 2016 11:51:02 +0100 > > Cameron Murdoch <cam at macaroon.net> wrote: > > > > > On 2 September 2016 at 09:53, Rowland Penny via samba
2009 Jul 05
1
mbox sync failure2
Hello, list, I'm new here and also new to Dovecot. On Friday evening (perhaps not the best moment...) I sent the following question but it seems to have been lost somehow: Yesterday I had to reboot my server machine and I think there was an email client connected from the LAN during the reboot which I did not notice then. Now that mailbox is no longer accessible: as soon as I try to