search for: encrypted_timestamp

Displaying 5 results from an estimated 5 matches for "encrypted_timestamp".

2019 Sep 02
2
Problem to access from Win to Win after classicupdate to Samba DC 4.10.7
...e this is not a problem for this ml, otherwise let me know where I can post my question. I have look into mit_kdc.log and I have see this recurred lament, (that I don't know what it means and whether it is important or not): set 02 11:54:36 s-addc.studiomosca.net krb5kdc[6764](info): preauth (encrypted_timestamp) verify failure: Preauthentication failed set 02 11:54:36 s-addc.studiomosca.net krb5kdc[6764](info): AS_REQ (6 etypes {aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-hmac(23), DEPRECATED:arcfour-hmac-exp(24), (-135), DEPRECATED:des-cbc-md5(3)}) 192.168.1.102: PREAUTH_...
2019 Sep 02
0
Problem to access from Win to Win after classicupdate to Samba DC 4.10.7
...t work, or give problems and you might have found another one. > > I have look into mit_kdc.log and I have see this recurred lament, (that > I don't know what it means and whether it is important or not): > > set 02 11:54:36 s-addc.studiomosca.net krb5kdc[6764](info): preauth (encrypted_timestamp) verify failure: Preauthentication failed > set 02 11:54:36 s-addc.studiomosca.net krb5kdc[6764](info): AS_REQ (6 etypes {aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-hmac(23), DEPRECATED:arcfour-hmac-exp(24), (-135), DEPRECATED:des-cbc-md5(3)}) 192.168.1.102: PRE...
2016 Jan 06
2
Authentication to Secondary Domain Controller initially fails when PDC is offline
On 1/6/2016 10:56 AM, Ole Traupe wrote: > Ok, I updated resolv.conf as you said. Then I restarted the network > service on this member server and afterwords suspended the 1st DC. > Now, kinit gives me again: > > "Cannot contact any KDC for realm 'BPN.TU-BERLIN.DE' while getting > initial credentials" > > Ole > > > Am 05.01.2016 um 13:41 schrieb
2016 Jan 07
0
Authentication to Secondary Domain Controller initially fails when PDC is offline
...92] 1452162654.272939: Encrypted timestamp (for 1452162654.272886): plain 301AA011180F32303136303130373130333035345AA10502030429F6, encrypted 0587DE7E7028F2F0FA2301D9752568B10A38B2612FFBCF1E45238C54655F2590A6BDA0B7892D871D74D01F0C6A8FB8D98189C827FB508E6D [25392] 1452162654.272964: Preauth module encrypted_timestamp (2) (flags=1) returned: 0/Success [25392] 1452162654.272970: Produced preauth for next request: 2 [25392] 1452162654.272991: Sending request (276 bytes) to my.domain.tld [25392] 1452162654.275253: Resolving hostname dc2.my.domain.tld. [25392] 1452162654.276241: Sending initial UDP request to dgram...
2019 Sep 01
2
Problem to access from Win to Win after classicupdate to Samba DC 4.10.7
I have do a classicupdate from a NT4 style domain to Samba DC 4.10.7 BIND_DLZ without (apparently) problem All seem work fine, access to PC work, join or re-join a PC to domain work, access from a Linux samba member server to Win7 PC work, access from Win7 to samba member server work. But I cannot access from a PC with win7 to another PC with win7. If I try to access from win7-0 to win7-1 via