similar to: NTP and FreeBSD jails

Displaying 20 results from an estimated 9000 matches similar to: "NTP and FreeBSD jails"

2020 Jul 30
2
NTP and FreeBSD jails
FreeBSD-12.1p7 Samab-4.10.15 running in FreeBSD Jail I just wish to ensure that my conclusion respecting Samba, FreeBSD Jails, and NTP is correct. 1. Unless configured otherwise Windows domain clients will query and obtain their time from the samba_server DC. 2. Samba_server obtains its time from the OS, in this case a FreeBSD Jail. 3. FreeBSD Jails get their time from their host. 4. If
2020 May 05
1
Samba-4.10.13 IPv6 turn it off
I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016
2020 Jul 13
5
DC replications of FreeBSD samba-4.10.15
On Sat, July 11, 2020 04:32, Andrea Venturoli wrote: > On 2020-07-10 14:47, James B. Byrne wrote: >> FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: > > Can you post the smb.conf of both DCs? > > Just out of curiosity, are you also using vfs_zfsacl? Yes. smb.confs DC1 and DC2: /zroot/iocage/jails/smb4-1a/root/usr/local/etc/smb4.conf [root at vhost04 ~ (master)]#
2020 Jul 22
1
samba-tool domain backup offline fails
On FreeBSD-12.1p7 running Samba-4.10.15 I have a working test AD domain. While samba_server is confirmed stopped the 'samba-tool domain backup offline' command gives the following error: [root at smb4-1c-testfmso ~ (master)]# hostname smb4-1.brockley.harte-lyne.ca [root at smb4-1c-testfmso ~ (master)]# samba-tool domain backup offline --targetdir=/tmp ERROR(<class
2020 Jul 22
3
samba-tool domain backup offline stalls
FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%
2020 Jul 13
3
DC replications of FreeBSD samba-4.10.15
On Mon, July 13, 2020 10:23, Andrea Venturoli wrote: > On 2020-07-13 15:06, James B. Byrne wrote: > >>> Just out of curiosity, are you also using vfs_zfsacl? >> >> Yes. > > But only on DC1, AFAICT! > I see no mention of it on DC2's smb.conf. > That could be the reason why you have two different behaviour. > > bye > av. > That appears to
2020 Jul 23
3
samba-tool domain backup offline stalls
On Thu, July 23, 2020 16:50, Rowland penny wrote: > Port 137 should only be used by Samba nmb, so has nmbd somehow > been started ? No. The error is not caused by anything else listening on 137. [root at smb4-2 ~ (master)]# netstat -an | grep -i listen tcp4 0 0 192.168.18.162.22 *.* LISTEN tcp4 0 0 192.168.216.162.22 *.*
2020 Jul 08
6
How to delete an unwanted NS record
On Wed, July 8, 2020 04:23, Rowland penny wrote: > On 08/07/2020 08:50, Mani Wieser via samba wrote: >> >> On 07.07.2020 22:14, Mani Wieser via samba wrote: >> Found it (while having my morning walk with the dog): same as with >> SOA: this is a zone/domain thing and not record >> >> Usage: samba-tool dns delete <server> <zone> <name>
2020 Jul 10
2
DC replications of FreeBSD samba-4.10.15
FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: On Fri, July 10, 2020 02:29, Andrea Venturoli wrote: > On 2020-07-09 21:36, James B. Byrne via samba wrote: >> set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_PARAMETER. >> ERROR(runtime): uncaught exception - (3221225485, 'An invalid parameter was >> passed to a service or function.') > > What
2020 Jul 23
2
samba-tool domain backup offline stalls
On Wed, July 22, 2020 14:48, Rowland penny wrote: > On 22/07/2020 19:40, James B. Byrne via samba wrote: >> >> On Wed, July 22, 2020 12:35, James B. Byrne wrote: >>> FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. >>> >>> When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: >>> >>> running backup on dirs:
2020 Jun 08
2
Samba AD-DC on FreeBSD-12.1 Jail
I decided to scrap everything and restart from the very beginning. I created a new jail. I installed samba410 samba-nsupdate py37-dnspython as these are current. I provisioned a domain: samba-tool domain provision --adminpass=INstall166 --dns-backend=SAMBA_INTERNAL --dnspass=INstall166 --domain=BROCKLEY --host-name=SMB4-1 --host-ip=192.168.8.166 --option="bind interfaces only=yes"
2020 Jun 29
1
Need help resolving or understanding these error messages in smbd.log
I am down to reconciling these last few samba_server startup messages in smbd.log: Item 1. [2020/06/29 11:29:49.887167, 1] ../../source3/printing/printer_list.c:234(printer_list_get_last_refresh) Failed to fetch record! We do not use samba as a print server and no printers are defined for that host. How do we turn off this message? Item 2. [2020/06/29 11:29:49.900481, 1]
2020 Jul 22
0
samba-tool domain backup offline stalls
On Wed, July 22, 2020 12:35, James B. Byrne wrote: > FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. > > When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: > > running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc > Starting transaction on /var/db/samba4/private/secrets > I tried the backup online option instead and
2020 Aug 24
4
core dump from samba-tool when chnging user password
On Mon, August 24, 2020 13:51 +0000, Rowland penny wrote: > It isn't a PDC, that is something quite different ;-) > I know, but it is a lot shorter to write than the DC possessing the PDC FSMO role. > It is your first DC. Not really, I have been working with MS AD Domains since NT 3.51, or whatever it was called back then. This one just happens to be the one I am currently
2015 Mar 10
2
Fail2Ban Centos 7 is there a trick to making it work?
On Mon, March 9, 2015 13:11, John Plemons wrote: > Been working on fail2ban, and trying to make it work with plain Jane > install of Centos 7 > > Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB > of disk space. Very generic and vanilla. > > Current available epel repo version is fail2ban-0.9.1 > > Looking at the log file, fail2ban starts and stops
2020 Aug 24
4
core dump from samba-tool when chnging user password
On Mon, Aug 24, 2020 at 11:57 AM James B. Byrne via samba < samba at lists.samba.org> wrote: > > > On Mon, August 24, 2020 11:17, James B. Byrne wrote: > > > > On the other hand, the errors I report are likely solvable should > someone with > > the ability to do so take note of them, so I am reporting this one. > What I > > want to know is whether this
2016 Oct 11
2
Samba 4.3.11 on FreeBSD-10.3 - Firefox problem on Win7Pro
We have recently converted our users from a Windows2000Advanced Server AD-DC to a Samba-4.3.11. AD-DC. For the most part this went very well, saving only for the degree of ignorance respecting things MicroSoft evidenced by myself. However, one of our users persistently reports difficulties with their roaming profile. Specifically, their Firefox profile. This did not occur before the change-over
2020 Jul 03
1
samab-4.10 nsupdate
I am also seeing this in smbd.log: [2020/07/03 09:20:18.211558, 1] ../../auth/kerberos/gssapi_helper.c:391(gssapi_check_packet) GSS VerifyMic failed: A token had an invalid MIC: unknown mech-code 2529638943 for mech 1 2 840 113554 1 2 2 [2020/07/03 09:20:18.211625, 0] ../../source4/auth/gensec/gensec_gssapi.c:1347(gensec_gssapi_check_packet)
2020 Jul 23
3
samba-tool domain backup offline stalls
On Thu, July 23, 2020 14:36, Jeremy Allison wrote: > The samba binary has an nbt server turned on > by default. It has a different functionality > set than nmbd. The jail is not running anything other than sshd and webmin, as the netstat results clearly show. The issue appears to me to be that samba-tool cannot bind to that port even though it is available. -- *** e-Mail is
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