Re: REMOTE DESKTOP NOT WORKING ANY LONGER PLEASE HELP!

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: nessus report
    ... when i ran nessus against my bsd box, nessus can detect "the remote host ... There are several ways to detect if a host is up. ... Sometimes services will respond differently if they're firewalled than if they're not listening on a particular port. ...
    (freebsd-questions)
  • Re: Need Help Fast.......
    ... to host... ... I checked the port 3389 is listening and open. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Port 80 is Open on My System
    ... I guess you choose Connect> Remote System... ... In the host name I ... I've tried all sorts, even connecting for a ... 80" - note the Space between the IP address and the port number. ...
    (comp.security.firewalls)
  • Re: Socket programming question.
    ... it assigns a new port number and provides the connecting ip address, ... the listen could be on port 80, but the link is random and could be on port ... I am new to socket programming and I have been searching on ... that controls the starting and stopping of listening to a socket. ...
    (microsoft.public.win32.programmer.networks)
  • Re: hosts.allow ?
    ... sshd: 62.149.232.105: deny ... to the hosts.allow file, but I see that this host is still making ... block the IP from connecting to the port, ... that listens on the port from allowing this IP to authenticate. ...
    (freebsd-questions)