similar to: winbindd fails to start

I have abandoned trying to get an existing AD-DC on a FreeBSD host using UFS to replicate successfully to a FreeBSD host on ZFS. I am now in the process of provisioning a new domain on the ZFS host. The domain is created on a FreeBSD thick jail using IOcage as the jail manager; probably should be called the warden but I digress. I have successfully provisioned a new domain but I see an issue

Rowland Penny rpenny at samba.org Fri Aug 9 15:25:00 UTC 2024 On Fri, 9 Aug 2024 10:40:18 -0400 "James B. Byrne via samba" <samba at lists.samba.org> wrote: >> 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) >> >>

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

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

Hi Rowland, do you maybe have any idea what could potentially cause this bug? smbclient thrwos me back a mount error(5): Input/output error when I try to mount the remote smbFS. It doesn't happen with my MacOSx and Windows 7 as client but it happens with Linux OSs and with a Konica Minolta copy machine with a scanner to samba function. The first try to mount fails with the above error.

I have a dc configured to use the samba internal dns service. The version of samba I am using is 4.10.15 packaged for FreeBSD. Its build options state this: BIND911 : off BIND916 : off , , , GSSAPI_BUILTIN : on GSSAPI_MIT : off LDAP : on . . . NSUPDATE : off My smb4.conf file contains this: [global] bind interfaces only = Yes dns forwarder =

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

FreeBSD-12.1p7 Samba-4.10.15 The user profiles were transferred from the existing Samba AD-DC to a new domain running on Samba-4.10. An ls on the original Samba (4.3.13) domain DC shows this: [root at SAMBA-01 ~]# ls -ld /var/samba4/BROCKLEY-2016/PROFILES/lyneak_hll.V2 drwxrwx---+ 16 BROCKLEY-2016\lyneak_hll BROCKLEY-2016\domain admins 512 Aug 12 17:07

On 23/07/2020 18:12, James B. Byrne via samba wrote: > > On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: > >>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~

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"

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:

On Fri, 8 Mar 2024 12:00:08 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > but the only thing apparent is that you appear to be running an EOL > version of Samba. Yes I know. Upgrading means stoppping 64 users. I'll do that ASAP. > Please post the smb4.conf. grep -v '#' /usr/local/etc/smb4.conf [global] security = ADS netbios name = HERMES server

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

Greeting- It has been years since I last set up a Samba server. The last one I did was a 2.x version! For the last two weeks I have been fighting with 2 issues with a samba 4 server I have set up for testing. . Encrypted transport seems to not work for me . Unix user smith and Samba user smith seem to have different UID numbers when files are created. At the moment the second issue is the

Hi, I’ve been searching online for a few days and am still hurting for an answer, otherwise I wouldn’t jump into a list and start asking questions straight away. We’re a 99% Mac shop running El Capitan (10.11.4). We’d been running Samba 4.2.3 on FreeBSD 10.0/ZFS for a while with minimal problems. I recently upgraded to 4.2.11 because of Badlock. Now when users create a new folder then try to

On 9/16/20 2:27 AM, Andrew Walker wrote: > > > On Tue, Sep 15, 2020 at 2:58 PM Budi Janto via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > Hi, > > For 3 days uptime serve about 40 client Windows workstation with traffic > average 50 Mbps - 80 Mbps (Video streaming) running on FreeBSD system > with 16

OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot

On 23/07/2020 18:36, Jeremy Allison wrote: > On Thu, Jul 23, 2020 at 06:31:09PM +0100, Rowland penny via samba wrote: >> On 23/07/2020 18:12, James B. Byrne via samba wrote: >>> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: >>> >>>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>>>> Failed to bind to

On 2/17/2016 5:00 AM, Rowland penny wrote: > On 17/02/16 00:03, Ian wrote: >> I've recently attempted to migrate some windows server files over to >> samba 4 hosted on a FreeNAS server. >> >> Using robocopy with the /copyall switch, I expected everything, >> including ACL's and ownership information to transfer over. For the >> most part they have.

On Fri, 8 Mar 2024 12:34:48 +0100 Luciano Mannucci via samba <samba at lists.samba.org> wrote: > > Hello all, > > I've added a new user to my AD in windows, but I cannot use it on my > freebsd machine using samba 4.12. I can see it via wbinfo but not > with id or getent. All prevously created users do work as expected. > Where should I look for the problem? >