Re: Remote Desktop with GPO
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 30 Oct 2005 23:56:14 -0600
Try connecting to the server by it's IP address and verify that RDP is
enabled in System properties/remote - allow users to connect to this
computer remotely. Run netstat -an to verify the server is listening on
port 3389 TCP, verify that you can ping the server from the client computer,
and that it can access port 3389 TCP. One easy way would be to use the
telnet command from the client as in telnet xxx.xxx.xxx.xxx 3389 where
xxx.xxx.xxx.xxx is the IP address of the server. If port 3389 is available
to the client it will get a blank command prompt screen with a blinking
cursor and if it is not if will get a connect failed message after perhaps
10 seconds. If not then there may be a firewall between the two which could
be the Windows Firewall on the server. --- Steve
"The Saint" <thesaint@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BD968B10-175F-4D99-9EF8-D49FFBEF1451@xxxxxxxxxxxxxxxx
>I have set up a GPO linked to an OU to "Allow administrators to connect
> remotely through Terminal Services" but when I try and connect to the
> computers within this OU with an administrator account, I get a message
> stating that the computer might not be available or remote desktop is not
> enabled. I am not using the server to try and connect to these machines,
> could this be the problem...I can use any other machine to connect, right?
>
> Anything helps...
> --
> The Saint
> MCP, MCDST
.
- Prev by Date: Re: user have multiple PCs
- Next by Date: site specific GPO
- Previous by thread: Re: Remote Desktop with GPO
- Next by thread: Re: Remote Desktop with GPO
- Index(es):
Relevant Pages
|
