search for: gerard_seibert

I know that this has probably been asked before. As a long time user of Samba, I remember using SWAT to configure Samba. It did seem, at least to me, to simplify things. At the very least, it did prevent me, and possibly other users, from creating simple syntax errors. I know that the Samba developers decided long ago to depreciate (eliminate) SWAT from the Samba distribution. I was just

I am having a problem with getting smbclient to interact with a Window 10 PRO/64 bit machine. The smbclient is being run from a FreeBSD-11.1/amd64 machine. smbclient - Version 4.6.11 Windows 10 Pro - version 1709 I have tried numerous methods, like the following: smbclient -I 192.168.0.102 -L HP-ENVY protocol negotiation failed: NT_STATUS_CONNECTION_RESET In every instance, it ends with the

I am running samba 4.6.11 of a FreeBSD 11.1 machine. This machine is part of a mixed network. I just updated one of the machines to the Windows 10 Fall Creators Update, version 1709. Now, the samba enabled machine no longer appears in the "Network" on the MS Machine; although I can reach it by manually typing in its network address, "\\Net_Bios_Name". I got this from the

Freebsd 12.0-RELEASE-p10 samba 4.8.12 Recently, my machine has started going into an endless loop with the following message rolling off the screen continuously: nmbd_subnetdb:make_subnet() Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address

samba 4.11.13 FreeBSD 11.4-RELEASE-p4 I was force to do a completely new installation of FreeBSD on a new HD. Everything is working fine, except for samba. When ever a file is transferred, this error message lights up the screen: Sep 22 07:10:05 scorpio smbd[77669]: remove_share_mode_lease: leases_db_del failed: NT_STATUS_OK It never happened on the old machine. I have no idea what is causing

Samba 4.8.9 FreeBSD 12.0-RELEASE-p3 / amd64 Since updating both FreeBSD and Samba, I have been getting the following screen pop-ups incessantly. They are always the same except for the time. IP 102.168.0.102 is a Win10 PRO / amd64 machine. I never received any warnings before updating. <quot> Mar 19 08:23:58 scorpio nmbd[11202]: [2019/03/19 08:23:58.049153, 0]

On Tue, 19 Mar 2019 13:02:40 +0000, Rowland Penny via samba stated: >On Tue, 19 Mar 2019 12:37:08 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> Samba 4.8.9 >> FreeBSD 12.0-RELEASE-p3 / amd64 >> >> Since updating both FreeBSD and Samba, I have been getting the >> following screen pop-ups incessantly. They are always the same

FreeBSD 12 Samba 4.8.12 Samba is not showing up on my Win 10 PRO machine. I can access the shares if I use the machines hostname or IP, though. How can I determine what version of ?smb? is being used? I have set ?client max protocol = SMB3? in the config file; however, I am not sure if it is being used. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was

FreeBSD 11.3 p7 /amd 64 rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, no prealloc, file-flags In an

On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: >On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client

On Thu, 20 Dec 2018 16:59:54 -0800, Jeremy Allison stated: >On Thu, Dec 20, 2018 at 12:08:02PM +0000, Gerard Seibert via samba wrote: >> Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a >> ZFS file system. >> >> I have a Windows 10 machine configured to do automatic backups to my >> FreeBSD machine on a daily basis. Since updating

On Fri, 18 Jan 2019 12:14:47 +0000, Rowland Penny via samba stated: >On Fri, 18 Jan 2019 11:15:38 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> FreeBSD 12.0-RELEASE-p2 GENERIC amd64 >> samba48-4.8.7 >> >> Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced >> a problem with samba. While still on FreeBSD 11,

FreeBSD 12.0-RELEASE-p2 GENERIC amd64 samba48-4.8.7 Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced a problem with samba. While still on FreeBSD 11, I configured a Windows 10 machine to write backups of selected directories to my FreeBSD machine. That worked perfectly. No problems were detected and everything was backed up correctly. However, after updating to FreeBSD 12 a

Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a ZFS file system. I have a Windows 10 machine configured to do automatic backups to my FreeBSD machine on a daily basis. Since updating FreeBSD, the following errors are displayed when the backup begins. This is a truncated list. Dec 19 06:29:01 scorpio smbd[56795]: [2018/12/19 06:29:01.413635, 0]