• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 339
  • Last Modified:

Extremely short Terminal Server lockout

When logging in to a terminal services session on a remote Domain controller, I am always able to successfully log in. However, the lockout is being invoked after less than a minute of activity, regardless of account being used. I do not have this extremely short lockout configured anywhere in Terminal Services Configuration, Terminal Services Manager, or Group Policy. I can't think of any other place where this value could be configured. Also, I see no events in the security event log that would indicate any problem. There is an avent 1030 in the Application event viewer: "Windows cannot query for the list of Group Policy objects," but I don't think it is related, since I believe that is a known error and has an associated hotfix. Any ideas?
0
bdbuchanan
Asked:
bdbuchanan
  • 4
  • 2
  • 2
  • +1
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
Check the settings on the Sessions tab for your user account properties in AD. You can set timeout and session limits in there.
0
 
rjwesleyCommented:
Does this occur when logged in to your TS via any workstation?

Rob
0
 
bdbuchananAuthor Commented:
acbrown2010: Sessions permissions are wide open; never disconnect.
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
bdbuchananAuthor Commented:
rjwesley: Yes, it happens from any workstation. Also, I have several other remote domain controllers, none of which has this problem.
0
 
Adam BrownSr Solutions ArchitectCommented:
What is your screen saver timeout set for on those systems? (Out of curiosity)
0
 
bdbuchananAuthor Commented:
acbrown2010: 15 minutes.
0
 
rjwesleyCommented:
Can you have someone test the terminal server connection that is physically at the remote site, does the lockout occur in that situation as well.
Are you using custom ports for each of your servers for terminal server connections?

Rob
0
 
bdbuchananAuthor Commented:
The solution was related to our drive encryption utility being incorrectly configured.
0
 
Glen KnightCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now