search for: johannesa

...: 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 >-----Oorspronkelijk bericht----- >Van: johannesa at celluloid-vfx.com >[mailto:samba-bounces at lists.samba.org] Namens Johannes Amorosa >| Celluloid VFX >Verzonden: donderdag 26 maart 2015 12:29 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] TSIG error with server: tsig verify failure > >Hi Louis > >On 03/26/...

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

Hello List, we have a running (test) AD samba4 system running successful for several month. We are now trying to add more DCs to the mix and have a proper backup/desaster recovery strategy. Basically I wan't to adapt the samba_backup script found in the sources to backup everything via git into our repository. I understand that the best solution would be to tar everything before commit. In

Hello Johannes, Am 18.12.2014 um 12:23 schrieb johannesa: > Basically I wan't to adapt the samba_backup script found in > the sources to backup everything via git into our repository. > I understand that the best solution would be to tar > everything before commit. You don't have to use tar. But you have to ensure, that you have a ba...

...e info.. OS used? compiled samba or binaries used from OS or Sernet Samba ? samba version? ( 4.1.17 ) The output of you bind9 config files. and the output of the smb.conf and the provisoning.. done how? best is the line u used. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: johannesa at celluloid-vfx.com >[mailto:samba-bounces at lists.samba.org] Namens Johannes Amorosa >| Celluloid VFX >Verzonden: donderdag 26 maart 2015 12:00 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] TSIG error with server: tsig verify failure > >Sry for digging up this old...

...or private folder to create online dumps of all ldb. But the dumps are smaller than the original. Is that ok? I'm in doubt regarding integrity. Am 20. Dezember 2014 10:59:59 MEZ, schrieb Marc Muehlfeld <mmuehlfeld at samba.org>: >Hello Johannes, > >Am 18.12.2014 um 12:23 schrieb johannesa: >> Basically I wan't to adapt the samba_backup script found in >> the sources to backup everything via git into our repository. >> I understand that the best solution would be to tar >> everything before commit. > >You don't have to use tar. But you have to en...

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

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

...lsrv_op_ > pull_source_apply_changes_trigger) > Mar 27 11:46:21 S4 samba[2791]: Failed to commit objects: > WERR_GENERAL_FAILURE/NT_STATUS_INVALID_NETWORK_RESPONSE > > > > > ---------- Mensaje reenviado ---------- > From: "Johannes Amorosa | Celluloid VFX" <johannesa at celluloid-vfx.com> > To: samba at lists.samba.org > Cc: > Date: Fri, 27 Mar 2015 13:14:35 +0100 > Subject: [Samba] Replication error after trying to sync sysvol > I tried to synchronize the sysvol folders, on two dcs. Something went > wrong since yesterday we have replicatio...

...lsrv_op_ > pull_source_apply_changes_trigger) > Mar 27 11:46:21 S4 samba[2791]: Failed to commit objects: > WERR_GENERAL_FAILURE/NT_STATUS_INVALID_NETWORK_RESPONSE > > > > > ---------- Mensaje reenviado ---------- > From: "Johannes Amorosa | Celluloid VFX" <johannesa at celluloid-vfx.com> > To: samba at lists.samba.org > Cc: > Date: Fri, 27 Mar 2015 13:14:35 +0100 > Subject: [Samba] Replication error after trying to sync sysvol > I tried to synchronize the sysvol folders, on two dcs. Something went > wrong since yesterday we have replicatio...

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

Hello List, we are using a 4.1.19 samba on ubuntu 12.04.3 (3.13.0-32-generic #57~precise1-Ubuntu SMP) on our fileserver (and as our ad dc on another machine) we're distributing 3 smb shares (/share/1, /share/2, /share/3). We have a project management that dynamically links active projects from the raid: /mnt/1/projectxy --> /share/1/projectxy /mnt/2/projectxy --> /share/2/projectxy

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

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 List, we like to add a newly generated user account that was created with the domain user tools, to another service on a separated machine, with the same credentials. Is there a simple way to retrieve the password like the username (%u) to hand the (cleartext-) password over to our adduser script? I know this is a hack, but we want to have a soft transformation until our AD service is

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 /var/log/samba/log.samba: Not authoritative for 's-static.ak.facebook.com', forwarding /var/log/samba/log.samba: Not authoritative for 's-static.ak.facebook.com', forwarding

Found the problem. There is a DNS Problem on one machine. This happend because I was testing some samba AD settings in a virtual machine, without knowing that NAT isn't shielding this properly - this vm propagated the "new" IP to one of the dcs. DC04> ping DC03 gives wrong IP! This should be fixable with the samba-tool dns update? On 03/27/2015 01:14 PM, Johannes Amorosa |

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

Hello List, we're having a problem mapping groups to a second server acting as a Fileserver. We use tdbsam with local users and groups on the pdc. We now want to add more servers to the setup, authenticating all users/groups via the domain. Adding the appropriate users and groups and do the mapping of uid and gid on the fileservers will be automatically done via ssh with a usradd.sh

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 -