|
Posted by Jason Rivers on July 13, 2007, 8:12 am
Please log in for more thread options
just noticed, on the server (the terminal server) under start >
Administrative tools > Terminal Services Configuration: then click
connections and right click RDP-tcp and click "properties, there is a
"Permissions" tab, but I can only see "local" users, and if I try and change
the system, it only see's itself and not the domain for the userlist. I'm
guessing this needs to be told that the "DOMAIN\Remote Desktop Users" group
is permitted to log on to that system? but how do I do that if I can not see
the DOMAIN for the system list?
/J
> I'm having a similar issue,
>
> We have a Terminal Services system: the system is headless and sits in a
> server rack, the machine was fine, allowed users to log on, this is for
> VPN users to have a desktop in the office. the system is running Windows
> server 2003 R2 SP2, it has just been set to be a MEMBER of our domain, so
> that users don't have to change their passwords in multiple places, and
> now the users can not log in, I get the message saying "to log on to this
> computer, you must be granted the allow log on through terminal
> services....." the user is a member of "Remote Desktop Users" on the
> domain controller, if I set the user into the "administrators" group, they
> still can't log on, but if I change to "Domain Admins" then they can. this
> is a problem as it is a terminal system, there is no physical access to
> the system.
>
> I also don't know how to set "logon at server" for the user, and will this
> still work given the server is not a domain controller but a member of the
> domain?
>
> /J
>
>> OK, where can I to config "logon at server" for the user, adding it to an
>> OU
>> or how?. Thanks a lot.
>>
>>
>>
>>> I'll ask you again: can the user in question logon to the actual,
>>> physical
>>> server in question. directly, not through remote desktop? If he cannot,
>> then
>>> you should provide, not full administrator access, but just "logon at
>>> server" in addition to making him a "remote desktop user".
>>>
>>> /Al
>>>
>>> > Yes, with the user "administrator" I can open a remote desktop
>>> > session,
>>> > and
>>> > if I add the user that can not logon
>>> > thru terminal server to the administrators group, he can access thru
>>> > terminal server. Thanks.
>>> >
>>> >
>>> >
>>> >> Can you open a remote desktop session using an account having local
>>> >> administrator rights on the server? Can the user in question logon
>>> > directly
>>> >> at the server? It could be that one needs logonAtServer privilege in
>>> >> addition to remote desktop privileges. Or alternately, could there be
>>> >> some
>>> >> policy in place that denies him access?
>>> >>
>>> >> /Al
>>> >>
>>> >> > He is attempting to connect to 2003 Server thru Terminal Server
>>> >> > from
>> a
>>> > XP
>>> >> > desktop, and he is memnber of "remote desktop users" group on the
>>> > server.
>>> >> > Thanks.
>>> >> >
>>> >> >
>>> >> >
>>> >> >> Which group did you at the user to, the "remote desktop users"
>>> >> >> group
>>> >> >> on
>>> >> > the
>>> >> >> server, in the domain, or on the workstation from which the user
>>> >> >> is
>>> >> >> attempting to open an RDP session on?
>>> >> >>
>>> >> >> /Al
>>> >> >>
>>> >> >> > Yes, I added to that group, and It does not work.
>>> >> >> >
>>> >> >> >
>>> >> >> >> Are you saying that you added the user to the group named
>>> >> >> >> "Remote
>>> >> > Desktop
>>> >> >> >> Users?" That's the group that Windows creates by default and
>> should
>>> >> > work.
>>> >> >> >>
>>> >> >> >> Hi! I have a user on a 2003 Server wich is member of group
>> "users".
>>> > I
>>> >> >> >> made
>>> >> >> >> this user member os group "users of remote desktop" to allow
>>> >> >> >> this
>>> > user
>>> >> > to
>>> >> >> >> logon from terminal server, but when I try it, appears a window
>>> >> >> >> telling
>>> >> > I
>>> >> >> >> can't login because I have no permission. What can I do?.
>>> >> >> >> Thanks.
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
| 
XML Sitemap