Re: Cannot Log Remotely Being a Remote User

Hello Vera,
Any chance I could pay you to fix this? if so, please tell me how to
contact you personally.

Yes I did check the allow users, deny is left unassigned, is this
right?

Well, I hope my users group permissions are well assigned, How could I
check it? All seems normal. Yes I am using the MMC and the right tools
to do it, the funny part is that everything worked fine. I am in the
way to setup a mirroring server and I am afraid it will copy the
current domain policies and deny remote administration too. Will this
happen?


Regards.

On 18 feb, 15:20, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
OK, since this server is also a DC, I assume that you have added the
account to the domain-wide Remote Desktop users group, correct? And
you are user the Active Directory Users and Computers tool to do
that?
Have you checked the user rights assignments in the Default Domain
Controller policy, especially
"Allowlogon through Terminal Services"
and
"Denylogon through Terminal Services"

Be sure to make careful notes of any changes that you make, make only
one change at a time and test its results before changing something
else!

Note that it is *not* recommended to run Terminal Services on a DC!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

ramon.talav...@xxxxxxxxx wrote on 18 feb 2007 in
microsoft.public.windows.terminal_services:



Hello again,
I installed vnc on the server, I have checked rdp-tcp
connection and
it does have the remote desktop group, I also checked the domain
an local group policies (security/user profiles) and checked
that the Remote Desktop User Group and the domain administrator
are listed there. Icannotaccess the local groups manager as
this is a Domain Controller. Results:CannotLogRemotely
because the Administrator is not a member of the remote desktop
users group, but he is in fact a user of this group. I also
created another user (REMOTEADMIN) and assigned it to the Remote
Desktop Users group.. same for him, no access.

Help me :). Is there anyway to reset those groups to their
normal security access parameters?. All this started when I
wanted to deny the permission to add computers to the domain to
normal users.. I did not change many things, and I have checked
all policies related to Terminal Services.

I want to give the remote users group the ability tologin
remotelyagain :).

On 15 feb, 23:35, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
I'm not sure that you can get to the permissions settings on
the rdp-tcp connections, if you changed something there which
now prohibits your access.
The fastest way to get access to the server is probably by
temporarily installing a vnc server on it, like TightVNC.
You can create a batch file to install most vnc servers
silently from the command line and thenremotelyschedule a job
on the server to run the batch file.

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

ramon.talav...@xxxxxxxxx wrote on 15 feb 2007 in
microsoft.public.windows.terminal_services:

Yes, I think I probably did, I did not type the exact error
message as it is in Spanish. But basically it is "A local
policy does not allow you tologinremotelyunless you are a
member of Remote Users Group, contact your administrator to
be added and pray he has not missconfigured the server".

How may I access the rdp-tcp connection properties remolety?
the machine is 250 miles from here and Icannotphisically
reach it until Saturday. I have remote access and the remote
admin pack installed, but no Terminal Services Configuration
icon, any chance to change itremotelyby means of other
graphical interface? I have remote group policy management,
may I do it with it?

Thanks, really.

On 14 feb, 23:02, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
Did you change the permissions on the rdp-tcp connection? Is
the Remote Desktop Users group still listed there?

If that doesn't solve it, can you post the *exact* error
message that you get?
Is there anything in the EventLog on the server?
Is it running Terminal Services, or just Remote Desktop for
Administration? Is RDfA still enabled?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

ramon.talav...@xxxxxxxxx wrote on 14 feb 2007 in
microsoft.public.windows.terminal_services:

Hello,
I am trying to access a Windows 2003 Server machine, It
tells me that
Icannotlogremotelybecause I am not a Remote-Group user ,
but I am! I am also the domain administrator. I have
checked several times the terminal services related GPOs
for the local machine and default domain and everythings
seems normal. I accessed the computer locally and added
the administrator directly as an allower remote desktop
user by means of the control panel/system/remote
gui.Cannotlogto the computerremotely..

Could someone give me a check list of what should I check
for the computer to accept my rdp connections?

If not, would it be good to reset the GPOs to the default
configuration? would it be safe? An active directory
restore would bring things to normal?

I suspect that I changed something that Icannotclearly
remember and probably it is it what is making it
difficult. What should I check to ensure that remote user
group is being acceptedremotely?

Help will be apprecciated really.

Best Regards,
Ramon- Ocultar texto de la cita -

- Mostrar texto de la cita -


.

Relevant Pages

  • Re: Remote Users on Virtual Machines?
    ... This offers most of the traditional desktop functionality while keeping all the processing power on the local server. ... You still need a client whether it's a thin client like Wyse offers or an old PC turned into a thin client or simply their workstation/laptop. ... The advantage of terminal services is that the applications are installed once and shared amongst all users connecting. ... I mistakenly thought TS and VM went hand in hand, so what should I be looking at to give me the functionality the remote uses have now using RWW through the SBS box WITHOUT a physical PC? ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Desktop vs Terminal Services
    ... TS has been enabled from Windows Components in add/remove. ... Users are members of the 'BackOffice Remote Users' group and I have tried ... adding this group manually to 'Allow logon to terminal services' through ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services 128 day or not?
    ... remote connects + 1 console session. ... Terminal Services is used to support normal users. ... by centralizing applications, etc vs desktops. ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: SBS2003 - Primary partition space limitation on DELL server
    ... Regarding your Remote Desktop question, you can install a Windows Server ... 2003 box as a member server with Terminal Services in Application mode. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot Log Remotely Being a Remote User
    ... account to the domain-wide Remote Desktop users group, ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
Loading