Re: The remote connection has timed out.

2009-07-28 Thread James Rankin
Stupid question - have you set up the user for access by adding them to the Remote Desktop Users group on the remote server? Do you have Restricted Groups GPOs that may have changed the group memberships after you have changed them? If that is correct then try using gpresult or the RSOP tools to

RE: The remote connection has timed out.

2009-07-28 Thread Richard Stovall
Try configuring: Computer Configuration Windows Settings Security Settings User Rights Assignment Allow logon through Terminal

RE: The remote connection has timed out.

2009-07-28 Thread Pierre Camilleri
Hi Richard I've checked the GPO settings and there is nothing configured for Terminal Services so no settings should be applied. The remote server belongs to a third party. It's a demo server which we need to connect to via Remote Desktop in order to view a demo of a software application.

Re: The remote connection has timed out.

2009-07-28 Thread James Rankin
If you are not an administrator and/or owner of this server, surely the owner should configure it so you can connect to it? 2009/7/28 Pierre Camilleri pierre.camill...@fosterclark.com Hi Richard I've checked the GPO settings and there is nothing configured for Terminal Services so no

Re: The remote connection has timed out.

2009-07-28 Thread Pierre Camilleri
But my account allows me to connect because I have admin rights. It is when normal users try to connect that they are getting the error message hence my suspicions falling on some GPO settings. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~

RE: The remote connection has timed out.

2009-07-28 Thread Charlie Kaiser
... *** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *** -Original Message- From: Pierre Camilleri [mailto:pierre.camill...@fosterclark.com] Sent: Tuesday, July 28, 2009 6:53 AM To: NT System Admin Issues Subject: RE: The remote connection has timed

Re: The remote connection has timed out.

2009-07-28 Thread James Rankin
Is the account you are using to connect a local account on the server? If so then I would suspect it is simply the Remote Desktop Users group that is at fault. Have you checked the user right for Log On Through Terminal Services as suggested by someone else? Is the server a member of your domain,

Re: The remote connection has timed out.

2009-07-28 Thread Pierre Camilleri
This server does not belong to us. We were given temporary access to it in order to view a demo on it via Remote Desktop. The problem cropped up when one of our users tried to access it via Remote Desktop. However when I tried accessing it using my normal account because I am a system admin, I

Re: The remote connection has timed out.

2009-07-28 Thread James Rankin
Only thing I can think of is that your account's username and password matches an account on the server then. Maybe when they set it up, they added a user for you, but not anyone else? 2009/7/28 Pierre Camilleri pierre.camill...@fosterclark.com This server does not belong to us. We were given

RE: The remote connection has timed out.

2009-07-28 Thread Richard Stovall
or on the box itself. -Original Message- From: Pierre Camilleri [mailto:pierre.camill...@fosterclark.com] Sent: Tuesday, July 28, 2009 10:15 AM To: NT System Admin Issues Subject: Re: The remote connection has timed out. This server does not belong to us. We were given temporary access