Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 697
  • Last Modified:

Terminal Services log on rights disappear

Hi all,

I have recently set up several remote apps using Windows 2008 terminal Services.  This past Friday I finished setting up a tablet PC to use these remote apps and tested each of them.  This morning I grabbed it to do some more testing and I can no longer connect to the Terminal Server.  The error I get is:

"To log on to thie remote computer, you must be granted the Allow log on through Terminal Services right.  By default, members of the Remote Desktop Users group have this right.  If you are not a member of the Remote Desktop Users group or another group that has this right, or if the Remote Desktop Users group does not have this right, you must be granted this right manually."

I have checked my settings and everything is correct.  This user (and one other user who is having the same trouble) is a member of an AD group called "AR_TerminalServices" which, in turn is a member of the Remote Desktop Users group on the Terminal Server.  There are a dozen other users also members of the AR_TerminalServices group and none of them seem to be having this same trouble.  As a precaution I added the two problem users directly to the Remote Desktop Users group, but this made no difference.  Then I rebooted the Terminal Server thinking that there might be a corrupt database entry.  Nothing seems to allow these users to terminal service into this computer again using the RemoteApps.  I CAN do a normal Remote Desktop Connection into this server, even using the problem user account, but when I try the RemoteApps, I get a consistent failure.

What is going on?
0
cwickstrom
Asked:
cwickstrom
1 Solution
 
authen-techCommented:
Try this:
http://ts.veranoest.net/ts_logon.asp

hope that helps,

Todd
0
 
cwickstromAuthor Commented:
Todd,

Thanks for the response, but the problem wasn't a rights problem.  I could connect to the same TS with the same user from other computers - just not from two computers.  

However, I eventually found the problem.  I've been having trouble with wireless connections being slow at recognizing DNS information, so I started adding a hosts file to laptops that points to the terminal server and to my file server.  After setting up a couple individually, I decided to create a master version and copy it to each laptop.  Well, it turns out that the first two laptops with the copied hosts file were the problem ones and when I noticed that I had put in the wrong address for the terminal server, I was able to resolve the problem.  Essentially, the remote apps were trying to make a connection to the file server instead of the terminal server and, of course, TS rights were not set up there.

Problem solved!
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now