search for: 4fb1034b8753

...ttempt @ Fri Sep 23 14:41:00 2016 EDT was successful 0 consecutive failure(s). Last success @ Fri Sep 23 14:41:00 2016 EDT DC=DomainDnsZones,DC=domain,DC=local Default-First-Site-Name\PFDC1 via RPC DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 Last attempt @ Fri Sep 23 14:40:58 2016 EDT was successful 0 consecutive failure(s). Last success @ Fri Sep 23 14:40:58 2016 EDT CN=Schema,CN=Configuration,DC=domain,DC=local site-b\SOLDC1 via RPC DSA object GUID: 55e069f...

...6 EDT was > successful > 0 consecutive failure(s). > Last success @ Fri Sep 23 14:41:00 2016 EDT > > DC=DomainDnsZones,DC=domain,DC=local > Default-First-Site-Name\PFDC1 via RPC > DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 > Last attempt @ Fri Sep 23 14:40:58 2016 EDT was > successful > 0 consecutive failure(s). > Last success @ Fri Sep 23 14:40:58 2016 EDT > > CN=Schema,CN=Configuration,DC=domain,DC=local > site-b\SOLDC1 via RPC >...

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, >

...Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > Default-First-Site-Name\PFDC1 via RPC > DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > site-b\SOLDC1 via RPC > DSA object GUID: 55e069f5-4f47-415b-8fa4-a...

On 5/17/2020 1:43 PM, Rowland penny via samba wrote: > On 17/05/2020 16:54, James Atwell wrote: >> >> Strange results on a domain member >> >> jatwell at osticket:~$ net ads user info administrator -U administrator >> Enter administrator's password: >> create_local_private_krb5_conf_for_domain: smb_mkstemp failed, for >> file

Hey all, has anyone done dcdiag against his DC yet? It's made from a windows client on command line: dcdiag /s:<servername> What are your results? With me some of the tests were not successful, e.g. ForestDNSDomain. My dcdiag is German so its output would not be so helpful for the mailing list. So somebody else can do a check to compare? Thanks in advance Tim