similar to: Samba 4.3.11 on FreeBSD-10.3 - Firefox problem on Win7Pro

On Tue, Oct 11, 2016 at 02:56:38PM -0400, James B. Byrne via samba wrote: > 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

On Tue, October 11, 2016 19:06, Jeremy Allison wrote: > > > This doesn't sound like a Samba problem. If access for that user > was completely cut off, or got authentication errors, that sounds > like us. But > > "FF stops responding to javascript > calls and generally slows down to an unacceptable degree." > > doesn't sound like something a remote

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 *.*

On Wed, June 3, 2020 10:52, Rowland penny wrote: > On 03/06/2020 15:31, James B. Byrne wrote: >> >> samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca >> ALL -U administrator >> Password for [BROCKLEY\administrator]: >> Name=, Records=3, Children=0 >> SOA: serial=1, refresh=900, retry=600, expire=86400, minttl=3600, >>

On Thu, July 30, 2020 17:23, Robert Marcano wrote: > On 7/30/20 5:00 PM, James B. Byrne via samba wrote: >> 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

Now I am down to discovering the meaning of these entries in: /var/log/samba4/smbd.log: [2020/06/09 09:04:54.269011, 1] ../../source3/lib/messages.c:899(send_all_fn) send_all_fn: messaging_send_buf to 57458 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND [2020/06/09 09:04:54.269680, 1] ../../source3/lib/messages.c:899(send_all_fn) send_all_fn: messaging_send_buf to 57477 failed:

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>

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)

We have a Samba-4.3 AD-DC hosted on a FreeBSD-10.3 system. We have just discovered that for some reason our domain workstations are not synchronising their time with the AD-DC. We have not altered the default GPO nor have we created a special GPO to handle time services. I have been working on several of the domain clients and I cannot seem to get them to source from the Samba server. I have

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]

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

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

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

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)]#

I have created a Samab AD-DC on a FreeBSZD-10.3 host. The setup checks out and I am able to join the domain from a Win7 workstation and run the ADUC management console in RAST. I have opened the UNIX Attributed properties tab for "Domain Admins" in the ADUC and set the unix properties. However, I get this notice "UNIX Attributes Unwilling To Perform" and after making the

I am unable to get roaming profiles to work. I have turned on debugging and I believe that I have narrowed down where in the log file the problem is reported. However, I do not possess the knowledge necessary to understand what is going on. The situation is that assigning a new user the profile: //DC/PROFILES/%USERNAME% does not produce anything on the DC's filesystem. However, using the

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"

I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in the log.wb-<DOMAIN> file: ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) I suspect that this may caused by an ip4 address assignment clash as I am using the configuration and data structures copied from our running Samba-4.13 DC. When I run winbindd interactively I see this: #

I am doing some testing with XForms and I really need a separate instance of Firefox, one that shares nothing with my primary instance that has various reference works and web sites open, to test forms. Is this even possible? I have a sense from the small bit of testing that I have done that even with separate profiles and invoking the firefox process manually from different terminal windows

On Mon, March 23, 2015 05:24, Nux! wrote: > I find this very, very sad. > I find it unsavoury. We are recommending that acknowledged newbies subscribe to a service known for repeatedly and persistently violating its members' privacy? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited