Solved

Extremely short Terminal Server lockout

Posted on 2010-11-22
10
329 Views
Last Modified: 2012-06-27
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
Comment
Question by:bdbuchanan
  • 4
  • 2
  • 2
  • +1
10 Comments
 
LVL 40

Expert Comment

by:Adam Brown
ID: 34190077
Check the settings on the Sessions tab for your user account properties in AD. You can set timeout and session limits in there.
0
 
LVL 8

Expert Comment

by:rjwesley
ID: 34190236
Does this occur when logged in to your TS via any workstation?

Rob
0
 

Author Comment

by:bdbuchanan
ID: 34190484
acbrown2010: Sessions permissions are wide open; never disconnect.
0
Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

 

Author Comment

by:bdbuchanan
ID: 34190503
rjwesley: Yes, it happens from any workstation. Also, I have several other remote domain controllers, none of which has this problem.
0
 
LVL 40

Expert Comment

by:Adam Brown
ID: 34190514
What is your screen saver timeout set for on those systems? (Out of curiosity)
0
 

Author Comment

by:bdbuchanan
ID: 34190569
acbrown2010: 15 minutes.
0
 
LVL 8

Expert Comment

by:rjwesley
ID: 34214007
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
 

Accepted Solution

by:
bdbuchanan earned 0 total points
ID: 34500797
The solution was related to our drive encryption utility being incorrectly configured.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 35171035
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

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question