Displaying 9 results from an estimated 9 matches for "7caa4845e34d".
2017 Mar 29
5
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
...S_DOMAIN_CONTROLLER_NOT_FOUND (winbind -P). Windows' RSAT tools
also completely fail to connect to the domain.
Some of the old DCs started throwing "Failed to bind to uuid
e3514235-4b06-11d1-ab04-00c04fc2dcd2 for
e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5]
NT_STATUS_UNSUCCESSFUL" errors
Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')".
So… How the fuck do I recover from this? What's even wrong?
--
Mit freundlichen Grüßen, / Best Regards,
Sven Schwedas, Systemadministrator...
2017 Apr 21
1
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
2017 Sep 08
0
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
...this one, track down both uuid's, checkout which which
> hostname belongs with these.
>
> Going by the output of `samba-tool drs showrepl` and sam.ldb,
> the GUIDs are as follows:
>
> graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7
> graz-dc-bis 7e4973ba-4093-4523-a70f-7caa4845e34d (not in sam.ldb)
> graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea
> villach-dc-sem eb5f9772-cd8f-4cde-9629-f1898c94aedd
> villach-dc-bis e1569c90-50f9-4bb5-bd85-79145e3ff6fd
>
> villach-sem/bis want to replicate to the dead and removed
> graz-dc-bis for some reason, but don'...
2017 Sep 06
6
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
...yStudio can help
> a lot with cleanup of these kind of things.
>
> Currently I'm using the ADSI MMC snap-in, any downsides
> compared to ADS?
I dont know, never used ADS :-/
Track done these : GUID's, the hostname's, ipnumbers A and PTR records
7e4973ba-4093-4523-a70f-7caa4845e34d
d613fa11-064b-4bcc-ab01-20264f870f47
(how, see Verifying and Creating the objectGUID Record https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record)
And as suggested, do this first through the RSAT tools or samba-tools, try removing them with these tools first.
(how https://wiki...
2017 Apr 07
0
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
...OUND (winbind -P). Windows' RSAT tools
> also completely fail to connect to the domain.
>
> Some of the old DCs started throwing "Failed to bind to uuid
> e3514235-4b06-11d1-ab04-00c04fc2dcd2 for
> e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5]
> NT_STATUS_UNSUCCESSFUL" errors
>
> Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')".
>
>
> So… How the fuck do I recover from this? What's even wrong?
>
>
>
--
Mit freundlichen Grüßen, /...
2017 Sep 08
2
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
...me
> >>> belongs with these.
> >>
> >> Going by the output of `samba-tool drs showrepl` and sam.ldb, the
> >> GUIDs are as follows:
> >>
> >> graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7
> >> graz-dc-bis 7e4973ba-4093-4523-a70f-7caa4845e34d
> (not in sam.ldb)
> >> graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea
> >> villach-dc-sem eb5f9772-cd8f-4cde-9629-f1898c94aedd
> >> villach-dc-bis e1569c90-50f9-4bb5-bd85-79145e3ff6fd
> >>
> >> villach-sem/bis want to replicate to the dead and remo...
2017 Apr 20
2
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
...Windows' RSAT tools
>> also completely fail to connect to the domain.
>>
>> Some of the old DCs started throwing "Failed to bind to uuid
>> e3514235-4b06-11d1-ab04-00c04fc2dcd2 for
>> e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:7e4973ba-4093-4523-a70f-7caa4845e34d._msdcs.ad.tao.at[1024,seal,krb5]
>> NT_STATUS_UNSUCCESSFUL" errors
>>
>> Attempts to remove the new ADDC fail with "(2, 'WERR_BADFILE')".
>>
>>
>> So… How the fuck do I recover from this? What's even wrong?
>>
>>
>>
&g...
2017 Sep 11
0
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
...t; belongs with these.
>>>>
>>>> Going by the output of `samba-tool drs showrepl` and sam.ldb,
>>>> the GUIDs are as follows:
>>>>
>>>> graz-dc-sem 160f5a53-5c29-4a83-aeee-6cb1dbabeed7 graz-dc-bis
>>>> 7e4973ba-4093-4523-a70f-7caa4845e34d
>> (not in sam.ldb)
>>>> graz-dc-1b bcffbad8-1add-46b9-bf69-90e52c0f09ea villach-dc-sem
>>>> eb5f9772-cd8f-4cde-9629-f1898c94aedd villach-dc-bis
>>>> e1569c90-50f9-4bb5-bd85-79145e3ff6fd
>>>>
>>>> villach-sem/bis want to replicate t...
2017 Sep 05
4
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
> 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: