similar to: Setup of a new PDC with Samba 3.2.0

Most of this is generated by FreeNAS's gui, so I'll have to figure out how to override it. I know where the file is, but I don't know if changes I make to it will actually stick, but that's for a different forum :) Just curious, since I appear to be running a PDC, is there a way to have a standalone samba server, and just get the user/password information from LDAP without doing

Hi, in our setup, we have a number of AD domains with an exisiting one-way trust between the local domain of the system (which I will call LOCALDOM in the following) and the domain containing the user accounts (which I will call TRUSTEDDOM in the following). The domain controllers run Windows Server 2012. Beginning with samba 4.4 we have an issue with authentication through pam_winbind on the

Certainly: https://termbin.com/wr68 Thanks again! On 5/25/19 2:16 PM, Rowland penny via samba wrote: > On 25/05/2019 19:29, David Kowis via samba wrote: >> Hello! >> >> Running on FreeNAS 11 and my smb.conf (via testparm -v) is here >> https://termbin.com/v748 > > Do you want try again posting the smb.conf, but this time run 'testparm' > without the

On 5/26/19 10:14 AM, Rowland penny via samba wrote: >> Just curious, since I appear to be running a PDC, is there a way to have >> a standalone samba server, and just get the user/password information >> from LDAP without doing all the domain stuff? That's actually what I'd >> like to do. I don't need a domain controller. > > I sort of thought you

In an effort to improve my lot, I'm trying to move to a ldap backend for idmap synchronization when I deploy the new 3.0.25 version on my systems. In preparation for this, I've set up some test systems -- where I'm having some problems that I think others may be encountering (according to a few comments I've seen recently). In a nutshell, I believe I have set up my ldap

On 26/05/2019 02:04, David Kowis via samba wrote: > Certainly: https://termbin.com/wr68 > > Thanks again! > OK, you are running Samba as an NT4-style PDC, though you don't seem to think so, because you have 'server role = member server', so I would remove the 'server role' line. I would change 'server min protocol = SMB2_02' to 'server min protocol =

Hi all, I have a domain member server 3.6.6 running on debian7, authenticating against another debian7 + samba 3.6.6 in DC-mode. Both servers have user-accounts and groups on LDAP and resolve posix users using libnss-ldap. The groupmap is living on LDAP as well. The domain member server serves a share with ACL enabled. I got the upgrade to 3.6.X and idmap-updates working, but the old

Dear Samba & Users. I have spent some time going over the documentation, however I still no not fully understand what the cause is. I am focusing on Samba 3 by Example chapter 5 & 6 specifically Chapter 5 smbpasswd -w 123456 [root@node1 data]# smbpasswd -w 123456 Setting stored password for "cn=Manager,dc=ddesign,dc=com" in secrets.tdb Chapter 6 indicates in the smb.conf to

Well I am glad that there has been alot of input on this topic, alot of people are having different opinions but that is because we are not focusing with the problem at hand. The documentation provides full details on how to get samba + ldap working from scratch; but there seems to be a gap between chapter 5 & 6; Once again I will say I love this book; by far the best technical reference

I am trying to create a Samba Admin account in FDS as per the final steps of http://directory.fedora.redhat.com/wiki/Howto:Samba I've asked about this on the FDS mailing list with no luck, I am hoping someone here will be able to help me. I've created a file with contents: Administrator:x:0:0:Samba Admin:/root:/bin/bash I then ran: /usr/share/openldap/migration/migrate_passwd.pl

Hi! I so far succeeded in setting up a Samba NT4 DC with OpenLDAP backend. Unfortunately I get the following error message connecting a Windows XP client to the domain (translated from german): [...] The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.lohrmann.de [...] This is surely due to a

Hi all, I encounter a problem trying to join a Samba 3 domain with a Windows XP client. Checking the network traffic with Wireshark I can see that the client sends a logon request with an empty username and the samba server replies with "user unknown". This behaviour is the same no matter whether I try to join the domain via system properties or the netdom join command. I can find

Hi! I'm currently setting up a Samba 3 PDC. So far I managed to setup Samba with an OpenLDAP backend, but adding a user with the command "net rpc user add mg password -U root" results in the following error: Failed to add user 'mg' with: WERR_GENERAL_FAILURE. In the logfile it says: [2009/10/28 15:56:28, 0] passdb/pdb_ldap.c:ldapsam_create_user(5119)

I am running Samba ver 3.0.33 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice versa. I had also tried setting up trusts with

There may be several parts to the problem: 1. Winbind on Samba 3.4.x seems unable to allocate idmap entries (UID/SID or GID/SID) , whether or not the backend is LDAP or TDB. Winbind on Samba 3.0.x is able to create idmap allocation mappings with an LDAP backend. The two problems with Samba 3.0.x are as follows - "getent" would stop showing trusted users once the cache period

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

I'm hoping someone can help me with the following. I currently have 2 Samba fileservers version 3.0.23d joined to our corporate Active Directory. Clients currently are Windows XP. I'm asked to prepare to migrate XP to Windows 7. From testing it looks like Samba 3.0.23d is not compatible with Windows 7. Therefor I started testing with the latest RHEL5 version 3.0.33-3.1e.el5 on RHEL5.

Hi, we had this setup working for quite some time but after upgrading the samba package things look different: we now have the following samba/ldap setup: samba-3.0.34p1-cups-ldap openldap-server-2.3.43 the samba-ldap configuration is: doing parameter ldap suffix = dc=foo,dc=ch doing parameter ldap machine suffix = ou=Computers,ou=Samba,ou=system doing parameter ldap user suffix =

Hello list, Quick summary of the issue (repeated below after the details): Running 'wbinfo --user-info=markc' on either smb ads member server will return identical info. Running 'wbinfo --group-info=BUILTIN\\Users' returns different information on each server. I'd like to make mappings for BUILTIN consistent in case I ever use them. Background and details: I have a

I finally make it work. The problem was in my nss_ldap.conf file. I was missing a line indicating there were "user" accounts in two different OU : People and Machines. Once this was fixed, I could properly check the trust account with winbindd. in libnss_ldap.conf: nss_base_passwd = ou=People,dc=mydomain,dc=fr and after I added this line nss_base_passwd =