Hello all!
I am encountering a problem when trying to connect to a remote server
using the Windows XP Pro (SP2) Remote Desktop. The domain user keeps
getting the following error:
The remote connection has timed out. Please try connecting to the remote
computer again.
Now when I log on using
the Windows XP Pro (SP2) Remote Desktop. The domain user keeps getting the
following error:
The remote connection has timed out. Please try connecting to the remote
computer again.
Now when I log on using an account with admin rights this does not happen
which means that there seems
broader rights
than you intend to.
From: pierre.camill...@fosterclark.com
[mailto:pierre.camill...@fosterclark.com]
Sent: Tuesday, July 28, 2009 8:33 AM
To: NT System Admin Issues
Subject: The remote connection has timed out.
Hello all!
I am encountering a problem when trying to connect
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.
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
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! ~
~
...
***
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
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,
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
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
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
11 matches
Mail list logo
