Re: Can not log into my terminal server - logon error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm glad that you both solved your problem!
How about posting the solution here, to help future users?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"rz8168" <rz8168@xxxxxxxxx> wrote on 21 jun 2006 in
microsoft.public.windows.terminal_services:

Nevermind I solved the problem too.

rz8168 wrote:
How did you solve this problem? I have same issue but I could't
find figure out how to fix this. I have a test account that is
member of "Remote Desktop Users" and "Domain Users" group

Here's the list of what had been configured:

- TS isn't running on DC
- "Remote Desktop Users" and "Domain Users" groups is added to
the "test" account
- RDP Connections permission has "Remote Desktop Users" and
"Domain Users" group added to Allow permission
- "Deny this user permissions to log on to Terminal Server" in
account properties is NOT checked
- "Enable Remote Desktop" in account properties is checked
- "Allow Remote Desktop" on the server is checked
- "Remote Desktop Users" and "Domain Users" has added to "Allow
log on through terminal service" in Group Policy

After hours, I still can't figure out why it is not working.
Any suggestion is greatly appreciated. Thanks.

Phil Buzzette wrote:
If you refer back to my first post, I am not running Terminal
Server on my domain controller. I have fixed the problem
though. Thank you very much for all the help.

"Jeff Pitsch" wrote:

This server is a domain controller then? If so, that would
explain alot. Also if it is, you are creating a security
issue with having normal users logging onto a domain
controller.

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"Phil Buzzette" <PhilBuzzette@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:C8FA2793-F47A-4067-8C6C-D41C6808318A@xxxxxxxxxxxxxxxx
I am pretty sure I figured it out. I had to give them
access to the
connection through the terminal services configuration. I
had them as members
of the group on the local machine and it still didn't
work.

I have an OU created with specific log on usernames
that have a set GPO.

I mean that I have a domain controller that, through
active directory, I created a OU for the Terminal Service
Users. I created a GPO for the users as
a "lockdown" method.

"Vera Noest [MVP]" wrote:

Then you probably are not connecting to the console
session after all.

A console session (which is only available to
Administrators), is started by typing "mstsc /console"
at a command prompt.

If you just type "mstsc", or you use the Remote Desktop
Client, then you are *not* connecting to the console
session.

As the error messages says, your users must be members
of the local build-in group "Remote Desktop Users" on
your Terminal Server. Can you confirm that this is the
case? And what exactly do you mean with:

I have an OU created with specific log on usernames
that have a set GPO.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?UGhpbCBCdXp6ZXR0ZQ==?=
<PhilBuzzette@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 02 jun
2006:

I am not familiar with how to remove the console
option.

"Jeff Pitsch" wrote:

Simply remove the console option.

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"Phil Buzzette"
<PhilBuzzette@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:BE0FF4FC-D89F-4998-8460-CBFD444611AB@xxxxxxxxxxxx
m...
Not to be ignorant, but how do I go about
correcting this? I don't need administrators to
connect. The normal users simply need to log in to
run a simple time clock application.

"Jeff Pitsch" wrote:

the console session only allows administrators to
connect. the console session is not to be used by
normal users and is not controlled by TS in
application mode.

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"Phil Buzzette"
<PhilBuzzette@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:5108C880-5E85-42FB-B4EA-9DAC3798BDFD@microsoft
.com...
I am connecting to the console session and the
server is configured in
application mode.

"Jeff Pitsch" wrote:

Are you connecting to the console session? Go
to Run and type mstsc.exe
then hit enter, then try to connect. as well,
make sure you have terminal
services installed in application mode
(add/remove programs, windows components.

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"Phil Buzzette"
<PhilBuzzette@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:1846AB70-2CA4-4AC7-838C-764701030639@micros
oft.com...
"To log on to this 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 remote desktop
user
group does not have this right, you must be
granted this right manually."

I have my machine, my terminal server, and my
server with active directory.
I have an OU created with specific log on
usernames that have a set GPO.
When
I open up rdp on my local pc and remote into
my terminal server, I get
the
above error message. The user account that I
am using is not an admin,
but
is
a domain user and a remote desktop user. I am
wondering what I might be
missing. If I make the user a domain admin,
it works fine, but that will
not
work in my situation. Any ideas or
recommendations would be greatly appreciated.
Thank you in advance for
those who take the time to assist
me.
.

Relevant Pages

  • Re: Terminal Server Roaming Profiles and Outlook 2007
    ... Microsoft MVP - Terminal Server ... "Jeff Pitsch" wrote: ... Most companies especially large ones want the profile to be correct for each user, not showing someone else on splash screens, etc, especially when it comes to the use credentials when office shows who has a particular file open. ...
    (microsoft.public.windows.terminal_services)
  • Re: Group Policy TS User Home setting
    ... Jeff Pitsch ... Microsoft MVP - Terminal Server ... However the setup does not use any per-user account settings, such as terminal server home/profile settings, logon scripts are configured using GPO, folder redirection, ts roaming profiles and ts home is configured using GPO. ...
    (microsoft.public.windows.terminal_services)
  • Re: Cached profile not deleting
    ... Microsoft MVP - Terminal Server ... I should have added to my first message that this is the first time I have worked with terminal server. ... "Jeff Pitsch" wrote: ... being closed properly on your profiles thereby preventing them from being deleted. ...
    (microsoft.public.windows.terminal_services)
  • Re: WIndows 2003 Remote Desktop Does client have to have Admin rights?
    ... Remote Desktop Users ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Ron Boetger wrote on 14 maj 2007: ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP-Tcp permissions not viewable
    ... Microsoft MVP - Terminal Server ... Get support from the experts at your business ... Jeff Pitsch wrote: ...
    (microsoft.public.windows.terminal_services)