similar to: Samba anonymous dns forwarding

On 04/15/2016 04:36 PM, lingpanda101 at gmail.com wrote: > On 4/15/2016 10:08 AM, Johannes Amorosa | Celluloid VFX wrote: >> Hello, >> we're using sambas internal DNS server. >> >> Is there a way to get rid of these messages in logfiles: >> >> /var/log/samba/log.samba: Not authoritative for >> 'static.ak.facebook.com', forwarding >>

On 04/18/2016 07:09 PM, lingpanda101 at gmail.com wrote: > On 4/18/2016 12:52 PM, Johannes Amorosa | Celluloid VFX wrote: >> >> On 04/15/2016 04:36 PM, lingpanda101 at gmail.com wrote: >>> On 4/15/2016 10:08 AM, Johannes Amorosa | Celluloid VFX wrote: >>>> Hello, >>>> we're using sambas internal DNS server. >>>> >>>> Is

We finally managed to upgrade from samba 4.1 to 4.2.9 (sernet packages). We have two replicated samba ADs. After the upgrade everything seems to work as expected, but I'm constantly getting this error message in the logs. They weren't there before the upgrade: We used the Updating samba wiki entry as howto[1] The first dc logs this: Failed extended allocation RID pool operation -

On 04/08/2016 02:01 AM, Jeremy Allison wrote: > On Tue, Apr 05, 2016 at 09:28:12AM +0200, Johannes Amorosa | Celluloid VFX wrote: >> Hello Samba list, >> we have a problem that our proprietary application sometimes can't >> find files on our samba share. I'm hoping >> for some help on this list. >> >> Our setup is two ADs as replicated domain

Hello Samba list, we have a problem that our proprietary application sometimes can't find files on our samba share. I'm hoping for some help on this list. Our setup is two ADs as replicated domain Controller ( Ubuntu 12.04.5 LTS, Version 4.1.17-SerNet-Ubuntu-10.precise) and several domain member as file servers and mixed clients (~40 x Win7, Ubuntu and OSX). The ADs use internal DNS.

> 13 April 2016 at 16:49 > > Well, it sounds like you don't have a schema master, what does > 'samba-tool fsmo show' give as the owner for the SchemaMasterRole ? > > It might also help if you can give us an instance of what you are > trying to add to the schema. > > Rowland I had a SchemaMaster, it was the first DC and it showed it is the Master - but via

Hello samba users- I've got a long overdue update to my domain controllers. Currently my domain controllers are running samba 4.0.6 on Ubuntu 12.04. I would like to upgrade to 4.3.8. I've read through the update page (https://wiki.samba.org/index.php/Updating_Samba) and it seems to be pretty straightforward. Are there any other suggestions, particularly from users who have done a

On 04/18/2016 08:35 PM, Marc Muehlfeld wrote: > Hello Johannes, > > Am 18.04.2016 um 18:52 schrieb Johannes Amorosa | Celluloid VFX: >>> What log level are you currently using? >>> >> Log level 2, but basically we want to keep log level because we are >> debugging. > > Was Samba installed through rpm/deb or did you compile it? In that case > you can

when you read. : http://www.spinics.net/lists/samba/msg111972.html says: > >That output > ; TSIG error with server: tsig verify failure >is usually only seen when the internal DNS server is running. >It's a glitch, which can be ignored atm (all dyn. updates are done OK). > so if you dont want to see that error, switch to bind9_DLZ. Greetz, Louis

On 04/08/2016 08:36 AM, Johannes Amorosa | Celluloid VFX wrote: > We finally managed to upgrade from samba 4.1 to 4.2.9 (sernet > packages). We have two replicated samba ADs. After the upgrade > everything seems to > work as expected, but I'm constantly getting this error message in the > logs. They weren't there before the upgrade: > > We used the Updating samba

Hello, I still receive this error in my log.samba and when running '/samba_dnsupdate --verbose --all-names'. Has this been fixed completely? Searching through the archives I see this post https://lists.samba.org/archive/samba-technical/2013-February/090408.html. Using Samba 4.1.7 with Ubuntu Server 12.04. My understanding is the update still succeeds but the error is

Hi, right now we're wrapping "samba-tool user add somthing " in a script to add a user in our samba 4.1 AD environment. We're doing all kinds of (read-only) queries which works fine for us. We need more control so I want to get rid of this limitation and do our user management directly via ldap. I'm unsure which entries I need to set via ldap, so we don't break our

On Fri, 2016-04-08 at 15:20 +0200, Johannes Amorosa | Celluloid VFX wrote: > On 04/08/2016 08:36 AM, Johannes Amorosa | Celluloid VFX wrote: > > We finally managed to upgrade from samba 4.1 to 4.2.9 (sernet > > packages). We have two replicated samba ADs. After the upgrade > > everything seems to work as expected, but I'm constantly getting > > this error message

On 4/20/2016 5:14 AM, Johannes Amorosa | Celluloid VFX wrote: > > > On 04/18/2016 07:09 PM, lingpanda101 at gmail.com wrote: >> On 4/18/2016 12:52 PM, Johannes Amorosa | Celluloid VFX wrote: >>> >>> On 04/15/2016 04:36 PM, lingpanda101 at gmail.com wrote: >>>> On 4/15/2016 10:08 AM, Johannes Amorosa | Celluloid VFX wrote: >>>>> Hello,

I tried to synchronize the sysvol folders, on two dcs. Something went wrong since yesterday we have replication problems: One machine shows this, while the other one is happy. samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ourdomain,DC=com Default-First-Site-Name\DC03 via RPC DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479 Last attempt @

We're using quite successfully a samba 4.1 AD setup authenticating user. We have on an unregular basis mails that can't be delivered because dovecot-pam fails to verify the credentials. I'm trying to debug this and set the loglevel up to 3. I can see an error message being spammed in the log files and can't figure out what causes this. I expect a configuration error somewhere

Hi, maybe this thread should ask an even more general question: How are AD-DC admins supposed to test upgrades? If there is more than one AD-DC, an upgraded DC which causes problems cannot (must not) be restored from backup. This is one of the reasons why I do not want to switch to AD. A PDC *can* simply be restored from backup. It is even enough to switch back to the previous contents of

Hi Louis, answers are inline ... On 03/24/2015 03:48 PM, L.P.H. van Belle wrote: > Realm is advices to use UPPERCASE.. not obligated. ( but very advices yes ) I changed the config to uppercase and rebooted, no change in the logfiles. > > check the following outputs and post them back in the list ( if needed anonymized ) > > hostname -i 192.168.1.235 > hostname -s the-ad-hostname

On 04/19/2016 04:39 PM, Klaus Hartnegg wrote: > Hi, > > maybe this thread should ask an even more general question: > > How are AD-DC admins supposed to test upgrades? If there is more than > one AD-DC, an upgraded DC which causes problems cannot (must not) be > restored from backup. This is one of the reasons why I do not want to > switch to AD. A PDC *can* simply be

2015-03-27 14:00 GMT-04:00 <samba-request at lists.samba.org>: > Send samba mailing list submissions to > samba at lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.samba.org/mailman/listinfo/samba > or, via email, send a message with subject or body 'help' to > samba-request at lists.samba.org