edutech4schools Posted March 1, 2016 Author Posted March 1, 2016 OK in DNS in domain properties under 'Name Servers' it is listing the main server as unknown. If I click edit / resolve it does list the correct ip but has an error - an unknown error has occored. If I click apply it does take the IP. I am totally useless at DNS.
edutech4schools Posted March 1, 2016 Author Posted March 1, 2016 Think I may have fixed it but not sure how to test. something like dcdiag????
edutech4schools Posted March 1, 2016 Author Posted March 1, 2016 Running dcdiag and getting a load of errors. Going to open a new post.
SWFoto Posted March 6 Posted March 6 (edited) I've just had this start popping up on my server manager - Started around when we started adding to the group policy (a shutdown command to get the PCs to turn off on a morning). Anyone got a clue where to go with this? Edit: On an Afternoon not in the morning... Edited March 6 by SWFoto
jthompson Posted March 6 Posted March 6 If the user account you're seeing that under is in the Protected Users security group (good practice), then its Kerberos ticket will expire after 4 hours. Lock the session, then unlock (or otherwise cycle your login) to get a fresh Kerberos ticket and try again. GPMC in particular will handle that expired Kerberos ticket not very gracefully (i.e. is the first to throw up various "I'm broken!" dialogues and generally needs to be closed and reopened after the ticket is refreshed). ADUC by contrast will fail more silently in this regard, and a simple refresh (after getting a new kerberos ticket) is sufficient for that one.
SWFoto Posted March 6 Posted March 6 7 minutes ago, jthompson said: If the user account you're seeing that under is in the Protected Users security group (good practice), then its Kerberos ticket will expire after 4 hours. Lock the session, then unlock (or otherwise cycle your login) to get a fresh Kerberos ticket and try again. GPMC in particular will handle that expired Kerberos ticket not very gracefully (i.e. is the first to throw up various "I'm broken!" dialogues and generally needs to be closed and reopened after the ticket is refreshed). ADUC by contrast will fail more silently in this regard, and a simple refresh (after getting a new kerberos ticket) is sufficient for that one. Thanks jthompson, think I've figured out it's a lack of available memory - popped back in eventviewer far enough!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now