similar to: Fwd: Re: Fwd: dnsdomainzone replication failure

Displaying 20 results from an estimated 100 matches similar to: "Fwd: Re: Fwd: dnsdomainzone replication failure"

2014 Jul 24
0
Fwd: dnsdomainzone replication failure
Am 24.07.2014 10:53, schrieb C.Kindler: > > Hello Achim, > > having similar troubles as mentioned on > https://lists.samba.org/archive/samba/2014-July/182916.html in our domain > > > How to solve the replication error? > > Many thanks, > Chris > > ---------- Forwarded message ---------- > From: *C.Kindler* <kindc1 at gmail.com <mailto:kindc1 at
2016 Mar 12
4
samba-4.3.6 and talloc-2.1.6
I build new version of talloc-2.1.6 (build from external tarball) and samba-4.3.6. But if I provision domain by command samba-tool domain provision --realm=test.alt --domain test --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc --use-rfc2307 --use-xattrs=yes I got error: Fixing provision GUIDs ERROR(runtime): uncaught exception - pytalloc_reference_ex() called for
2016 Mar 12
0
samba-4.3.6 and talloc-2.1.6
On 12/03/16 14:20, Andrey Cherepanov wrote: > I build new version of talloc-2.1.6 (build from external tarball) and > samba-4.3.6. > But if I provision domain by command > > samba-tool domain provision --realm=test.alt --domain test > --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc > --use-rfc2307 --use-xattrs=yes > > I got error: >
2016 Mar 12
0
samba-4.3.6 and talloc-2.1.6
On 17:21:44 wrote Andrey Cherepanov: > I build new version of talloc-2.1.6 (build from external tarball) and > samba-4.3.6. > But if I provision domain by command > > samba-tool domain provision --realm=test.alt --domain test > --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc > --use-rfc2307 --use-xattrs=yes > > I got error: > Fixing
2018 May 15
0
migrating NT-style domain SID-error
On Tue, 15 May 2018 08:07:27 +0200 Stefan Kania <stefan at kania-online.de> wrote: > Good morning, > > today we started allover with a new machine, we got the same errors > but now we have an errormessage when doing a "samba-tool dbcheck" > --------------- > root at addc:~# samba-tool dbcheck > Checking 664 objects > ERROR(runtime): uncaught exception -
2019 Jul 03
0
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03/07/2019 15:50, Sven Schwedas via samba wrote: > It's amazing how long Samba just keeps running even when apparently > everything's broken. > > In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on > all of them, resulting in: > > graz-dc-sem: >> Checking 3861 objects >> Error: governsID
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error:
2013 Dec 03
4
Samba 4 DNS name Planing
Dear All, Can help to advise if there are any name planing for dns? e.g: I've a domain amtb-m.org should my samba4 server be ad.amtb-m.org? OR should I create another non-reachable internal domain e.g: ad.amtb-m.lan For them? What is the benefit on this or that? Any documentation about that? Thank you.
2018 May 15
1
migrating NT-style domain SID-error
Hi Rowland, after we solved the puzzle today here is what we found: The Samba PDC with tdbsam backend was installed a loooooong time ago. Many updates and distributions later, the Samba PDC was still running with with the same databases and the same smb.conf. The only thing that someone sometime changed was the hostname and the NetBIOS-Name in smb.conf. BUT in secrets.tdb was still the old name.
2014 Aug 01
2
DELL E6510 pxelinux issues
> Hello, > > On 24.07.2014 17:32, Gene Cumm wrote: > > On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: > >> On 24.07.2014 13:52, Gene Cumm wrote: > >>> As expected. You have a different OUI (the first 3 octets of the MAC > >>> address). Try everything from 6.03-pre18 and then lpxelinux.0 from > >>>
2014 Aug 27
3
DELL E6510 pxelinux issues
> Hello, > > On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: > >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> > wrote: > >>>> On 24.07.2014 13:52, Gene Cumm wrote: > ... > >>>> Your special build gets the gateway working, but the downloaded InitRD > >>>> still
2014 Aug 27
0
DELL E6510 pxelinux issues
Hello Ady, On 27.08.2014 16:46, Ady wrote: >> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >> wrote: >>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the
2014 Aug 27
0
DELL E6510 pxelinux issues
Hello, On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: >>>> On 24.07.2014 13:52, Gene Cumm wrote: ... >>>> Your special build gets the gateway working, but the downloaded InitRD >>>> still gets corrupted sometimes. Boot-time is down
2014 Jul 25
0
DELL E6510 pxelinux issues
Hello, On 24.07.2014 17:32, Gene Cumm wrote: > On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: >> On 24.07.2014 13:52, Gene Cumm wrote: >>> As expected. You have a different OUI (the first 3 octets of the MAC >>> address). Try everything from 6.03-pre18 and then lpxelinux.0 from >>> here:
2014 Aug 27
1
DELL E6510 pxelinux issues
On Wed, Aug 27, 2014 at 12:21 PM, Philipp Hahn <hahn at univention.de> wrote: > Hello Ady, > > On 27.08.2014 16:46, Ady wrote: >>> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >>> wrote: >>>>>>> On 24.07.2014
2018 May 14
5
migrating NT-style domain SID-error
Hello, after migrating a samba NT-style domain from Samba 4.2.14-debian (debian 8.10) to samba 4.5.12-debian (debian 9.4) We copied all tdb-files to the new machine plus the smb.conf plus /etc/group. The old Samba has tdbsam as backend. we use the same domain and hostname on the new DC as it was set on the old system. We are using bind9 as DNS-backend in the new system. The "samba-tool
2014 Jul 24
3
DELL E6510 pxelinux issues
On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: > Hello, > > On 24.07.2014 13:52, Gene Cumm wrote: >> On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de> wrote: >>> PS: <http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz> did not work. >> >> As expected. You have a different OUI (the first 3
2007 Aug 15
3
unit testing active resource - mock or connect?
Hi all - there''s a patch I need to apply from a ticket: http://dev.rubyonrails.org/ticket/8798 The ticket appears to be stalled on the lack of a test case. I figured I''d just whip one up, but because it''s an Active Resource thing, and the test case would need to do ModelName.find(:all), I''d need to either mock the network connection or set one up. In this
2004 Aug 06
2
Current Ices2 requirements?
I've been using Ices2 for quite a while with no real problems; fairly stable and does what I want it to. Can't ask for more, eh? :) Anyway, the latest checkouts of CVS won't even get past the ./autogen.sh/./configure portion, so I was wondering if the automake/autoconf requirements had changed recently. This is my setup: Gentoo Linux automake 1.7.5(-r2) autoconf 2.57(-r1) The -r*
2017 May 09
2
www-scripts Sphinx doc builder broken and needs intervention.
Hi Tanya, The www-scripts builder that updates the Sphinx documentation has been broken for about a week now, despite the buildbot builders passing. The error from the last sphinx update attempt says: > /opt/tools/sphinx_update.sh: warning: removing stale lock file from PID 8798. > UPDATING lld SOURCES > Updating '.': > At revision 302593. > make: *** No rule to make