similar to: Samba 3.6 -> 4.x and trusts

We already have a Openldap in production, with a samba3. What I am wanting to do is install the Samba4, and still continue to use the "openldap" for authentication of users in various services that are operating. You think it's possible? On Sat, Dec 6, 2014 at 2:41 AM, jacek burghardt <jaceksburghardt at gmail.com> wrote: > DO you mean using samba as ldap ? I am using

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]

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

Hi, Good day! I have a few questions regarding the status of Samba 3.6, I know it's now EOL but I'll ask anyway. We currently have a large install base of Samba version 3.6 at the moment in our environment and we can't migrate immediately. My question is, do you still release security patches (at least the highly critical ones) for Samba 3.6? Or is it completely unsupported now?

________________________________ 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

I greatly appreciate the answers. Are of great value to me and to others who like me do not have much experience. Another question. :D I believe that we will use debian as distribution for the new Samba4. What I need to copy from the old to the new distro? On Sat, Dec 6, 2014 at 12:49 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote: > On 06/12/14 14:32, Elias Pereira wrote:

Hello Marc, I appreciate your response, as well as the other members. Reading your answer, I believe I found what I wanted. Option 3, the principle is what I need right now. I'll try to explain. Today in production, we have the samba3 + openldap. The samba3 is installed on a freebsd, but has some problems that we can not detect. My boss does not want to drop the openldap now. We have

Hello I try to add a windows 10 client to a existent samba 3 domain. I have installed a windows 10 build 10049 with all Updates. On the windows client I added/modified the following Registry Keys that I can join to to the Samba 3 Domain. HKLM->System->CCS->LanmanWorkstation->Parameters DNSNameResolutionRequired = 0 DomainCompatibilityMode = 1 On the Samba Server I created the

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

Rowland, The *openldap* will be the same that is already working on our campus (technological courses). I have samba3 on a freebsd, but the samba4 I will switch to Debian. I believe that in addition to the *smb.conf*, I have to also copy the following folders: */etc/samba/* */var/lib/samba/* Proceeds? On Sat, Dec 6, 2014 at 2:23 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote:

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

Hello. My setup: _ one Samba 3.5 domain (XXXXXXXX), with a PDC and a BDC, both running FreeBSD; _ one AD domain (YYYYYYYY) running on two Windows 2003 DCs; _ bidirectional trust between the two domains. Everything used to work until I moved the PDC from Samba 3.5 (EOL'ed) to 3.6; now, users from domain YYYYYYYY cannot access the PDC's shares. I used to have in smb.conf: >

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

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

On 07/06/15 10:17, Rowland Penny wrote: >> > ldap machine suffix = ou=machines >> > ldap user suffix = ou=users >> > ldap group suffix = ou=groups >> >> 3.6 works without these, why shouldn't 4.2? >> AFAIK, these can help performance, but with 3 PCs and 5 users they >> should practically make no difference. >> BTW, in my case

On 2019-11-13 09:30, Andrew Bartlett wrote: > Regarding your problem, on linux I use lslocks to debug from here, you > can normally work out which process is holding the lock, which lock it > is waiting on (if any, marked with a *) and gdb that to work out what > is the matter with it, and perhaps why it is in that situation. Hmm... I have no lslocks on FreeBSD; will lsof do? In

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

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 Mon, 2017-05-15 at 18:58 +0200, Andrea Venturoli via samba wrote: > On 05/08/17 11:17, Andrea Venturoli wrote: > > Hello. > > > > I've got a network of FreeBSD servers which traditionally hosted a > > classic domain. > > I upgraded some months ago, removing the old PDC and BDC and migrating > > to an AD DC controller in a jail. > > This is