Re: REMOTE DESKTOP NOT WORKING ANY LONGER PLEASE HELP!

If the Vista machine is listening for incoming rdp traffic (on
whatever port you configure), it sounds to me as a firewall issue.
Try posting to a vista newsgroup, maybe you get more help there.

microsoft.public.windows.vista.general

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

=?Utf-8?B?TUk=?= <MI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 28 dec
2007 in microsoft.public.windows.terminal_services:

Yes the host is listening on port 3389 the default and I
verified this. I tried changing the listening port to 4000 and
trying to connecting using <IP>:4000 but still nothing.

"Vera Noest [MVP]" wrote:

I understand that you have checked in the registry *which* port
is used by rdp, but have you also verified that the host is
actually *listening* on that port?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TUk=?= <MI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 27 dec
2007:

The host is a vista machine and it is located at my house. I
have checked the port in the registry and also the firewall
exception as well. I am baffled by this problem.

"Vera Noest [MVP]" wrote:

OK, and it's the host that is running Vista, is that
correct? Have you checked if it is listening on port 3389,
with "netstat - an" at a command prompt? Is the host located
at your work? If so, have you contacted the network
administrator? There might be a centrally managed GPO which
disables Remote Desktop connections.
_________________________________________________________
Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TUk=?= <MI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 27
dec 2007 in microsoft.public.windows.terminal_services:

Vera,
Well I tried this from various computers. However I
tried now and no
still the same thing. My PC is configured through the
firewall as well through port forwarding. I cannot RDP
into it locally nor over the internet. I dont think the
problem is from the client pc but rather something on the
host that has disabled remote desktop function.

"Vera Noest [MVP]" wrote:

Does it also happen when you start the rdp client with
RunAs.. an use the Administrator account?
Can other clients connect to the same host?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TUk=?= <MI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
27 dec 2007:

The exact error I am getting when trying to connect is
"This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact
the owner of the remote computer or your network
administrator."

This pops up after about 20 seconds of trying to
connect.

Also that same day I noticed an X on my network
connection icon in the system tray... when I hovered
the mouse over it it said "Server execution error" so I
applied the following fix I found:
Right click "Computer"
Click "Manage"
Under the "System Tools" section, Double click "Local
Users and Groups" Click "Groups"
Right click "Administrators"
Click "Add to group..."
Click "Add"
Click "Advanced"
Click "Find Now"
Double click "Local Service"
Click "Ok"
"NT Authority\Local Service" should show up in the
list now Click "Ok"
Close Computer Management and reboot.

After this the error was gone, but the remote issue
started.

Thanks for your help!

"Vera Noest [MVP]" wrote:

There's no need to SHOUT :-)

How far do you get in the connection process? Do you
get an error message? What is the *exact* text? When
exactly do you get the message? Have you checked the
EventLog on the host PC? Any errors or warning there?
You might have to enable auditing on the host first.
When exactly did the problem start? What was changed
immediately prior to that? Did you run Windows Update?
Any other changes?
_______________________________________________________
__ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal
Server TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TUk=?= <MI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 27 dec 2007:

Hello, I am new to the boards and figured I would
try to see if anyone has had the same issue I am
having. I have Vista Ultimate, i been remoting in
forever. All of a sudden I cannot. I can ping the
PC I can access shares
I can ftp into it
I checked the RDP port in the registry
I checked the firewall

I have no clue whatelse to check. This has happened
to me on another PC before and I got so frusterated
I just rebuilt it.
I don't want to have to do this again, there has to
be an
explanation to this issue. Anyone have any ideas???
Thanks in advance!
.

Relevant Pages

  • Re: RDP over SSL question
    ... So after reading this article it sounds like as long as you are up on SP's ... RDP connections using SelfSSL to create the SSL certificate. ... RDP and TCP port 3389 so your firewall rules should not need to be ...
    (microsoft.public.windows.terminal_services)
  • Re: What is the trick to get Windows XP firewall to stay on (after a reboot)?
    ... > While I did not explicitly state that the EPRT and PORT commands reached ... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ...
    (microsoft.public.windowsxp.network_web)
  • Re: What is the trick to get Windows XP firewall to stay on (after a reboot)?
    ... > While I did not explicitly state that the EPRT and PORT commands reached ... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ...
    (microsoft.public.windowsxp.basics)
  • Re: What is the trick to get Windows XP firewall to stay on (after a reboot)?
    ... > While I did not explicitly state that the EPRT and PORT commands reached ... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ...
    (comp.security.firewalls)
  • Re: What is the trick to get Windows XP firewall to stay on (after a reboot)?
    ... > While I did not explicitly state that the EPRT and PORT commands reached ... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ...
    (microsoft.public.security)
Loading