Displaying 10 results from an estimated 10 matches for "8a7d".
Did you mean:
877d
2017 Mar 14
2
AD replication issue
...Last attempt @ Tue Mar 14 09:25:09 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:09 2017 CDT
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:25:06 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:06 2017 CDT
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168...
2017 Mar 13
2
AD replication issue
...nsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt@ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt@ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last...
2017 Mar 13
3
AD replication issue
...e9-9bffa9e413aa
>> Last attempt@ NTTIME(0) was successful
>> 0 consecutive failure(s).
>> Last success @ NTTIME(0)
>>
>> DC=DomainDnsZones,DC=mediture,DC=dom
>> epo\EPO-DC01 via RPC
>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
>> Last attempt@ NTTIME(0) was successful
>> 0 consecutive failure(s).
>> Last success @ NTTIME(0)
>>
>> DC=DomainDnsZones,DC=mediture,DC=dom
>> vsc\DC01 via RPC
>> DSA object GUID: da9bb168-47a0-4368-aff3-b...
2017 Mar 14
0
AD replication issue
...Tue Mar 14 09:25:09 2017 CDT was
> successful
> 0 consecutive failure(s).
> Last success @ Tue Mar 14 09:25:09 2017 CDT
>
> DC=DomainDnsZones,DC=mediture,DC=dom
> epo\EPO-DC01 via RPC
> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
> Last attempt @ Tue Mar 14 09:25:06 2017 CDT was
> successful
> 0 consecutive failure(s).
> Last success @ Tue Mar 14 09:25:06 2017 CDT
>
> DC=ForestDnsZones,DC=mediture,DC=dom
> vsc\DC01 via RPC
>...
2017 Mar 13
5
AD replication issue
I forgot to associate inter-site links (all using default), which fixed
a lot though I'm still having an issue.
* vsc site
o vsc-dc01
o vsc-dc02
* aws site
o aws-dc01
* epo site
o epo-dc01
* vsc-dc01 => anywhere: OK
* vsc-dc02 => anywhere: not replicating
* aws-dc01 => anywhere: OK
* epo-dc01 => anywhere: OK
I've tried with samba_kcc =
2017 Mar 13
0
AD replication issue
...1 via RPC
> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
> Last attempt@ NTTIME(0) was successful
> 0 consecutive failure(s).
> Last success @ NTTIME(0)
>
> DC=DomainDnsZones,DC=mediture,DC=dom
> epo\EPO-DC01 via RPC
> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
> Last attempt@ NTTIME(0) was successful
> 0 consecutive failure(s).
> Last success @ NTTIME(0)
>
> DC=DomainDnsZones,DC=mediture,DC=dom
> vsc\DC01 via RPC
> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
> Last attempt @ NTTIME(0) was success...
2017 Mar 13
0
AD replication issue
...Last attempt@ NTTIME(0) was successful
>>> 0 consecutive failure(s).
>>> Last success @ NTTIME(0)
>>>
>>> DC=DomainDnsZones,DC=mediture,DC=dom
>>> epo\EPO-DC01 via RPC
>>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
>>> Last attempt@ NTTIME(0) was successful
>>> 0 consecutive failure(s).
>>> Last success @ NTTIME(0)
>>>
>>> DC=DomainDnsZones,DC=mediture,DC=dom
>>> vsc\DC01 via RPC
>>> DSA object GUI...
2016 Oct 17
3
Replications errors on 4.5.0 (WERR_BADFILE)
Executing the following with nsupdate seems to have fixed replication.
update add 28f7281f-3955-4885-8a7d-42a36ee87590._msdcs.mediture.dom. 900 A 192.168.222.5
show
send
update add 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa._msdcs.mediture.dom. 900 A 172.16.1.106
show
send
update add fe066b13-6f9e-4f3c-beb4-37df1292b8cb._msdcs.mediture.dom. 900 A 192.168.168.65
show
send
New DNS records I create don't...
2016 Oct 14
2
Replications errors on 4.5.0 (WERR_BADFILE)
Replication has been running smoothly until I upgraded to 4.5.0. I had
various errors with all BDCs and a force sync didn't resolve it. I
shutdown all BDCs, demoted them with --remove-other-dead-server then
joined new BDCs with new names. At first replication was intermittently
failing (consecutive failures counter kept resetting), but it seemed OK,
just slow if anything. Now they all
2007 Nov 02
0
[PATCH] PVWin: Fix warnings
...ext time)
-- Andy
---------
diff -r b26bdba50c41 common/include/evtchn_public.h
--- a/common/include/evtchn_public.h Thu Nov 01 16:21:24 2007 -0700
+++ b/common/include/evtchn_public.h Fri Nov 02 09:52:30 2007 -0700
@@ -21,7 +21,7 @@ DEFINE_GUID( GUID_XEN_IFACE_EVTCHN, 0xD2
//{D2D20756-DE69-4447-8A7D-9837197D6166}
typedef evtchn_port_t
-(*PXEN_EVTCHN_ALLOCUNBOUND)(int Domain);
+(*PXEN_EVTCHN_ALLOCUNBOUND)(domid_t Domain);
typedef NTSTATUS
(*PXEN_EVTCHN_BIND)(evtchn_port_t Port, PKSERVICE_ROUTINE
ServiceRoutine, PVOID ServiceContext);
diff -r b26bdba50c41 common/include/hypercall.h
--- a/co...