similar to: Windows 2012 EOL

Hello. I've got a Samba server and I'd like it to be master browser and everything else except domain controller (the customers wants a workgroup, not a domain). Lately a Windows 2003 server was added to the net and then I guess it was removed. I keep getting messages like the following in the logs: > Apr 10 03:07:51 apocalypse nmbd[57552]: [2005/04/10 03:07:51, 0]

A conclusion to this episode. In the end W2016 Essentials became problematic, in that when installed, it "demands" to become the ADDC controller. Yes, it is possible to remove all the ADDC controller "stuff" and make it a W2016 Essentials domain member server but, that removal process was complicated, to say the least. W2019 Essentials is a stripped down, use as a domain

On 05/03/16 22:55, Rowland penny wrote: > Don't use freebsd, but Samba 4, when run as an AD DC, uses nsupdate to > update a computers DNS records in AD. First off, thanks for answering. Alas, I don't really understand what you mean... Is it used to dynamically add A records for clients that connect to the AD? >> Is it intended to work with BIND (like the other two in

On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > Possible things to check: > Is the ip for vlan1 10.1.2.34 ? Sure. It's the only IP vlan1 has inside the jail; it's shown as an alias on the base host. > Try just setting 'vlan1' You mean change "interfaces=vlan1 10.1.2.34/24" to just "interfaces=vlan1"? It doesn't change anything (still

Hello. At a site I've got a domain with only one DC, which is Windows 2012. This OS will be soon out of support and must be replaced. The replacement will be Windows 2022 standard, but, for reason I won't dwell into, it shulud not be a DC. Is it possibile to migrate this domain to a Samba DC, then join the new server as a member? Will Samba 4.16 do? Basically, I would: _ follow this

On 20/05/2023 10:29, Andrea Venturoli via samba wrote: > Hello. > > At a site I've got a domain with only one DC, which is Windows 2012. > This OS will be soon out of support and must be replaced. > The replacement will be Windows 2022 standard, but, for reason I won't > dwell into, it shulud not be a DC. > > Is it possibile to migrate this domain to a Samba DC,

I know this might be half OT, but nontheless Samba is involved. A customer of mine has two Macs with Mac OS X 10.5 and is sharing a folder on one of them. We'd like to avoid any permission problem, so I put the followinf in smb.conf: create mode=0777 force create mode=0777 directory mode=0777 force directory mode=0777 This is usually enough to achieve what I want, with other OSes.

Hello. I'm using Samba 3.6 and two-ways trusts to a Windows 2003 domain. 3.6 will be EOLed soon, but 4.x doesn't seem to support trusts. Am I wrong? What's the suggested way to handle this? bye & Thanks av.

Hello. Forgive me, but I'm quite new to AD and I've been searching the web for a couple of days, but found nothing relevant... What's exaclty the NSUPDATE option of this port? Is it intended to work with BIND (like the other two in that group)? What are its requirements? Any reference to a tutorial or any other documentation on how to use it? bye & Thanks av.

Hello. I see a lot of people having this problem, but found not solution so far. The setup: samba 3.0.37 on FreeBSD 7.3/i386 acting as PDC; a similar BDC (only amd64) and XP clients. Users have roaming profiles on the PDC. What happens is: _ a laptop user disconnects from the network (so the local and server profiles are fully synchronized); _ at home [s]he deletes some files; _ back in the

Hello. I'm in need of some help to shed some light on a strange problem. The box is running Samba 4.1.7 on FreeBSD 9.2/amd64 and I suspect (though I'm not sure) all troubles started after the upgrade from 4.1.6. The setup is quite simple: no AD, no LDAP, only one server. A command as simple as "smbclient -U user //SERVER/SHARE", if fired up several times in a row on the

On Thu, 2019-04-04 at 08:38 +0200, Andrea Venturoli via samba wrote: > On 4/4/19 12:36 AM, Suporte - KONTROL via samba wrote: > > > > Hi Andrew, > > Thanks much for the message. > > > > As I am using FreeBSD 12, that´s the latest SAMBA version available > > via PKG support, although I know it's possible to compile the ver > > 4.10 > > Would

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

On 5/20/23 15:33, Rowland Penny via samba wrote: > You never mentioned Freebsd before, I take it all back, I do not know if > it will work, Samba as a DC on Freebsd is just too flaky (from what I > have observed) to trust. I've got 10 FreeBSD DCs running without any problem. Perhaps you are talking about some advanced feature I don't use? Auth works. Scripts do. I rarely used

Hello. I know this is half OS-specific: I already asked on freebsd-ports@, but got no answer so far... Since 3.6 has been EOLed I'd like to upgrade all my such Samba installations to 4.2. Right now I don't want to switch any of them to AD; I just want to keep running as I do now, but with a supported version. I've started from the simplest cases and so far I've been able to

________________________________ From: Uday Mhatre<mailto:uday_mhatre at hotmail.com> Sent: ?05-?12-?2014 12:58 To: Andrea Venturoli<mailto:ml at netfence.it> Subject: RE: [Samba] samba 2.2.7a tech issue Just wondering if these samba versions are backward compatible with fedora14 and other Linux distributions. Regards, Uday ________________________________ From: Uday

On 04/07/15 11:35, Andrea Venturoli wrote: > Hello. > > I know this is half OS-specific: I already asked on freebsd-ports@, > but got no answer so far... > > Since 3.6 has been EOLed I'd like to upgrade all my such Samba > installations to 4.2. > Right now I don't want to switch any of them to AD; I just want to > keep running as I do now, but with a supported

Hello. I'm seeing several of the above messages in my smbd logs. I see three different kinds: > close_directory: Could not delete share entry for . > close_directory: Could not delete share entry for {filename} > close_remove_share_mode: Could not delete share entry for file {filename} I could find no explanation on their meaning. Anyone has a pointer? bye & Thanks av.

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 For all those currently using BIND 8, please be aware of the notice below from ISC. Given that we have moved to BIND 9 for all of our releases from 5.x on (and BIND 9.4.x in 7-soon-to-be-release), and given that FreeBSD 4 was the last branch to have BIND 8, and itself is now EOL, the time has come to say good-bye to BIND 8. I will be

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