similar to: Logins differ for ip/DNS on ad dc

Thanks for the reply Rowland (and sorry for replying twice). I actually used the wiki you linked to setup the dc. I just added those idmap settings because getent could not list my samba users after setting it up, due to your mail I realised I only needed the winbind options to make it work. The original problem still remains though, using \\SMB.WIE I can only access netlogon and sysvol, using

On Sat, 05 Nov 2016 07:06:19 +0100 Maximilian Kirchner via samba <samba at lists.samba.org> wrote: > I set up a samba ad dc (self compiled samba 4.5.1 on Ubuntu 16.04). > If I connect to the server via \\smb.wie (its dns name) I can access > netlogon and sysvol. If I connect via its IP then I can access all my > shares (test as an example) - but either way I cannot connect to

Thanks a lot for your help so far. The main reason I do not use vms is that the server is pretty limited in RAM so this would only be my last resort. To prevent confusion: srv.wie (192.168.1.50) is the same machine as smb.wie (192.168.1.55), I seperated them just now to debug the problem. > These look like they are being run on the DC, what about from the > windows clients ? > I did

> > This sounds like a dns problem, are your windows machines using the DC > as their nameserver ? > yes they are using the server as dns. DNS is done through bind9 and implemented in samba via bind9_dlz. All looks fine: $ host -t A smb.wie smb.wie has address 192.168.1.50 $ host -t SRV _kerberos._udp.smb.wie _kerberos._udp.smb.wie has SRV record 0 100 88 srv.smb.wie. $ host -t SRV

There is no winbindd--it was never installed. I don't recall exactly why I didn't install it, but I seem to recall something about Samba4 in an AD domain control role not needing it. I ended up using SSS instead. Sanatized smb.conf: # Global parameters [global] workgroup = DCS realm = DCS.LOCAL netbios name = SERVER server role = active directory domain

On 19/04/16 21:08, Thomas Smith wrote: > It was my understanding that winbind wasn't necessary for Samba4. This > server has been running for months without it. > > Sanatized smb.conf: > > # Global parameters > [global] > workgroup = DCS > realm = DCS.LOCAL > netbios name = SERVER > server role = active directory domain

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

Hi for all! I have Samba 4.3.9-Ubuntu DC in ADDC_Mode and it's working perfectly But in Samba Log have this: "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." The libbsd-dev package is installed Is this a problem? SAMBA.CONF: # Global parameters [global] workgroup = TESTEAD realm = testead.xxxxx.xxx netbios name = GTESTE2

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server

Here's what I get at level 0 right after stopping/starting Samba: [2016/04/19 12:27:06.043469, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.3.8-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2015 [2016/04/19 12:27:06.157629, 0] ../source4/smbd/server.c:490(binary_smbd_main) samba: using 'standard' process model samba: setproctitle not

On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running

We have a Samba4 AD DC running on an Ubuntu 14.04 VM [ smb.conf ] # Global parameters [global] workgroup = MEADORANDCO realm = meadorandco.com netbios name = SOGO server role = active directory domain controller dns forwarder = 192.168.121.1 idmap_ldb:use rfc2307 = yes passdb backend = samba allow dns updates = nonsecure

I've been using Samba4 on Debian/Jessie since it became "stable". After the last upgrade however, I got a massive failure. The first symptom I noticed was that I couldn't grab updates from the Debian servers. However when clients tried to log in, the real problem revealed itself. They could only log on using a temporary profile and couldn't connect to any of the shares

Try : apt-get remove libbsd-dev restart samba, now is the message gone? Gr. Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens BasSamba via > samba > Verzonden: woensdag 15 maart 2017 16:09 > Aan: samba at lists.samba.org > Onderwerp: [Samba] samba: setproctitle not initialized, please either call >

Hello, Some users in my domain report that they have to use different (old) passwords on different computers. They say that they still have to use their "old" passwords after they changed it. My domain setup is that users are asked to automatically change their password on Windows 7 Enterprise after some months. So they have to do that. Otherwise they cannot login. But why is it, that

> > You are using Bind9 with flatfiles, this is NOT recommended. > If you are using the standard Ubuntu Bind9 package, you should be using > BIND9_DLZ and this stores the dns info in AD. > How did you provision the DC, was it with 'BIND9_FLATFILE' or > 'BIND9_DLZ' ? > If it was the later, just remove the 'wie' zone and its reverse zone > from the

Thanks to various contributors on the Samba List (particularly Rowland, Marc & Andrew), I have successfully configured a Samba AD DC on Ubuntu 14.04 from scratch and joined my Windows 2008 R2 Servers. However, I have had a recurring error from the beginning -- [2015/04/30 05:06:31.194379, 0] ../source4/smbd/server.c:370(binary_smbd_main) samba version 4.1.6-Ubuntu started.

On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01

Hi, after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence - task_server_terminate: [XXXd failed to setup interfaces] error messages in log.samba (I removed a couple of "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." lines for better readability): [2019/06/11 09:23:47.400171, 0]

Could I get some input regarding restoring ACLs? There's nothing in the Samba wiki about what to do with the ACL archive. I've finished all of the other steps already, what do I need to do to restore this archive? JS On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org> wrote: > On 03/03/16 20:33, IT Admin wrote: > >> I do have the 4.3.3 sources.