similar to: NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

Hai Sven, > -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: dinsdag 5 september 2017 17:13 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): > Server (GC/name/dom at DOM) unknown > > On

> -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: vrijdag 8 september 2017 14:40 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): > Server (GC/name/dom at DOM) unknown > > On 2017-09-08 10:37, L.P.H.

Today's episode of "why is AD break", brought to you by: > [2017/09/05 10:17:06.015617, 3] ../source4/auth/gensec/gensec_gssapi.c:613(gensec_gssapi_update) > Server GC/graz-dc-1b.ad.tao.at/ad.tao.at is not registered with our KDC: Miscellaneous failure (see text): Server (GC/graz-dc-1b.ad.tao.at/ad.tao.at at AD.TAO.AT) unknown > [2017/09/05 10:17:06.015717, 0]

Hai Sven, Sorry for the long wait, i had some things todo first here. > -----Oorspronkelijk bericht----- > Van: Sven Schwedas [mailto:sven.schwedas at tao.at] > Verzonden: woensdag 6 september 2017 16:06 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] Server GC/name.dom/dom is not > registered with our KDC: Miscellaneous failure (see text): >

> Keytabs look reasonable, as far as I can see, but why does > graz-dc-sem have the same SPN output as graz-dc-1b in > addition to its own? A snapshotted server/cloned server? I dont know but thats not correct. I suggest, cleanup the DS with FSMO roles. Then remove a failty server and re-add it as a new installed DC. ( the good DS with FSMO) First backup:

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Sven > Schwedas via samba > Verzonden: dinsdag 21 mei 2019 16:44 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Debugging Samba is a total PITA and > this needs to improve > > On 21.05.19 16:15, L.P.H. van Belle via samba wrote: > >> Since Cyrus

Okay, time to bring some order into this. == Keytab and replication == Editing servicePrincipalName cleaned up the keytab. Some things are even replicating correctly (modulo the missing host), others aren't. DNS replication (DC=ForestDnsZones and DC=DomainDnsZones) is still not working, at least one host is trying to connect to deleted servers for this. The other I cannot confirm because

The KDE screen savers will only blank out the screen though most of them test ok when you hit the test button in the Control Center. The Gnome screen savers work ok. My system has a Radeon 9200SE video card and I have a ViewSonic A70f monitor. Does anyone have a fix for this?

Hai Sven, And still i see/think you should change some things to get a better base setup. And no its not bike shedding.... It is making a standard setup, work from there. [libdefaults] default_realm = AD.TAO.AT dns_lookup_realm = true < if you have multple REALM, else false. (default_realm = AD.TAO.AT) dns_lookup_kdc = true Checking file: /etc/nsswitch.conf passwd: files

I am trying to hook up linux to an LCD 1333x768 LCD TV. XP in 1024x768 show up just fine. X does not. I have set the screen preferences to 1024x768. I have edited the xorf.conf file instead of have a range from 50 - 70 I change it to be only 60. I start X and it still comes up on my A70F monitor but still will not show on my LCD TV. xvidtune does not run on this PC. It says something about

Hello, i?ve Samba 4.7 with domain controller with 3 servers, 1 master (samba-ad) and two slaves (samba-slave1) and (samba-slave2). The problem is when create user account from "samba-ad? this account not sync to slave, but i create the account on "samba-slave1" or "samba-slave2? this is sync on all server. Samba version [???????.] root at samba-ad:~# samba -V Version

In the end I just upgraded all DCs to 4.5 and remote-deleted the broken ones. Seemed to work without a hitch, manual removal was only necessary to remove the IPs from DNS\_msdcs.ourdomain\gc\. I'll try adding new DCs on a date that's not "Friday two hours before I disappear for vacation". On 2017-03-29 16:51, Sven Schwedas via samba wrote: > Situation: Trying to upgrade

On 2017-04-07 13:44, Sven Schwedas via samba wrote: > In the end I just upgraded all DCs to 4.5 and remote-deleted the broken > ones. Seemed to work without a hitch, manual removal was only necessary > to remove the IPs from DNS\_msdcs.ourdomain\gc\. Apparently not, adding new DCs failed with "WERR_DS_DATABASE_ERROR". `samba-tool dbcheck --fix` solved that. With that out of

Hi, I need to create a data frame containing the results of a number of ANOVA's but I'm having some trouble setting it up (some being enough for me to spend 3 days trying with no progress and be left staring in to the abyss which some people call a weekend, and what I will call 2 quiet days in the office...) The response variable is *V*. I need to do an ANOVA for each *G*. The fixed

I believe the problem is a lack of outbound replication for non PDC emulator DCs. You'll notice isn't even trying because last successful was epoch (never) yet there are no errors. Inbound replication for this DC seems fine. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID:

On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack

On Mon, 2019-08-26 at 23:10 +0200, gizmo via samba wrote: > Ok, I understood, I should join with a new name. > But what's the difference between my plans and the docu "Rejoining the upgraded DC" ? > There is nothing mentioned, that a new name is necessary. > Is it because I install a new OS and so I start from scratch ? A new name is not necessary, which is why this

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead

On 9/21/2016 11:32 PM, Garming Sam wrote: > I would have assumed that deleting all the NTDS connections for all the > DCs would have remedied this issue. I'll write a patch to try to avoid > this error in any case. > > Ignoring this error and answering your earlier question, it's often hard > to tell if the KCC is doing what is expected or not. To figure that out, >