search for: as_rep

David A. Morrow wrote: >Hi all. I wonder if someone might be able to help with an issue which has recently begun plaguing >my network. All of my Linux machines are configured as domain member of a Windows 2000 Active Directory domain. Up until recently, all of these boxes were working correctly but all of a sudden, they have all stopped. All are Redhat Enterprise 3. All are using

...not being correctly resolved. This happens to ALL windows machines I join to the domain, and rejoining doesn't do anytihng. Purging kerberos tickets for 0x3e7 and trying to access a network share as LocalSystem (psexec -s -i -d cmd) to get a new one doesn´t work. I ran wireshark to examine the AS_REP and AS_REQ, and decrypted the TGT using an exported keytab from the linux server to check if the machine was being correctly identified and it was, even group membership was correctly included. wbinfo and getent from another linux server in the domain show correct id and group membership for the wi...

...g). Then my previous scenario (blocked_fw / kinit / smbclient -k -L rodc / clear_fw / smbclient -k -L srvads) worked liked a charm. However on the windows side, I still couldn't log on the rodc and I had the same windows error message as Michael Brown in his post [1] (even tough the AS_REQ/AS_REP was going fine, checked with log level= 9). Having no clue at all, I started to setup a clean testbed with sernet packages on a dedicated LAN to reproduce the issue and hire the sernet guys to have a developper to look at it. But I couldn't reproduce the issue in the testbed, everything was...

Hi Garming, > As far I know, all this should work as you would expect. Quite recently, > Andrew Bartlett and I went about testing some of the behaviour of the > KDC and confirming behaviour such as RODC ticket forwarding. thanks for the input. It gives me hope to dig deeper! I have some more time to spend on this issue today, I gonna try some more scenario. > The one thing to check