Displaying 7 results from an estimated 7 matches for "4bcc".
Did you mean:
42cc
2017 Mar 29
5
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption
too much by adding new DCs and demoting old ones.
After bringing online the first 4.5 DC, I ran `demote
--remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs
(held no FSMO roles). That seemed to run fine (the DC had been offline
for a few weeks at that point and I didn't want to restore it just for
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
2014 Dec 11
2
PJSIP configuration question
Dan Cropp wrote:
> I had my screenshots flipped. Is there a way to make sure the Contact field is NOT included in the ACK response to the OK (for the Answer)?
>
> PJSIP is including the Contact for the ACK response to the OK.
> Contact:<sip:1234 at xxx.xxx.xx.xxx:5060>
>
There is no configuration option to configure this behavior. What is the
full SIP signaling?
--
Joshua
2014 Dec 11
0
PJSIP configuration question
...ranch=z9hG4bKPjddc1c054-48ce-4714-ba4e-9690aa9be55b
From: <sip:b5a0e71d-9216-4f3c-aedb-a48ecd2fa642 at XXX.XXX.XXX.XXX>;tag=9c4172da-1b32-442b-bea0-75ca3530b661
To: <sip:64.2.142.93>
Contact: <sip:b5a0e71d-9216-4f3c-aedb-a48ecd2fa642 at XXX.XXX.XXX.XXX:5060>
Call-ID: 0817263d-519b-4bcc-aa11-a5bbd8c21f2f
CSeq: 20166 OPTIONS
Max-Forwards: 70
User-Agent: Asterisk PBX 13.0.0
Content-Length: 0
<--- Transmitting SIP request (487 bytes) to UDP:192.168.10.235:5060 --->
OPTIONS sip:291 at 192.168.10.235 SIP/2.0
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bKPj46636dcf-...
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
...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_Recor
> > d)
>
> Neither of the two return any results on any DC (or on the
> dnsmasq servers), but the GUIDs for th...
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
...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.samba.org/index.php...
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: