Can not connect via remote desktop

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My remote desktop connection was working fine within my LAN (all 192.168.x.x
IP's)
I turned the computer off for about an hour, turned it back on and I can not
connect using remote desktop. I have done google searches and just can not
find out why I can not connect. No software was installed nor any changes to
my LAN. The windows firewall was disabled and I can not telnet to port 3389
of the same computer. I went to my computer and allow users to connect
remotely does have a check in it.

Telnet <the ip address> 3389

It responds with:

Connecting to remotehost...Could not open connection to the host, on port
3389; Connect failed.

When I go to another machine on my LAN I get this error:

The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.
Please try connecting again later. If the problem continues, contact your
administrator.


This is driving me crazy, anyone know how to fix it?
Thanks
 
To make sure the port 3389 is listening, use this command: netstat -an |find /i "3389". More details can be found this page,
How to find open ports on a computer

http://www.howtonetworking.com/command/openport1.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
My remote desktop connection was working fine within my LAN (all 192.168.x.x
IP's)
I turned the computer off for about an hour, turned it back on and I can not
connect using remote desktop. I have done google searches and just can not
find out why I can not connect. No software was installed nor any changes to
my LAN. The windows firewall was disabled and I can not telnet to port 3389
of the same computer. I went to my computer and allow users to connect
remotely does have a check in it.

Telnet <the ip address> 3389

It responds with:

Connecting to remotehost...Could not open connection to the host, on port
3389; Connect failed.

When I go to another machine on my LAN I get this error:

The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.
Please try connecting again later. If the problem continues, contact your
administrator.


This is driving me crazy, anyone know how to fix it?
Thanks
 
Are you using a static private LAN IP for the PC you want to control with
Remote Desktop?

If not the IP probably changed when you rebooted the PC negating your port
forwarding scheme through your firewall/router...

http://www.portforward.com/networking/static-xp.htm

General setup and troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I am using static LAN NAT'ed IP address. When I open a CMD window and telnet
(IP address) 3389 it says connection refused but the NETSTAT window says
LISTENING. I have reset the windows firewall to default settings then
disabled it and same thing.
 
Are you running any type software like NAV worm protection or OneCare Live
that may be blocking RDP connections?

Some VPN client software causes issues like this. Are you running any VPN
client software on that particular PC?

Any messages in the event log when you try to connect from another PC?

Can you ping the PC by IP?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
It was the Norton blocking it. Thank you very much for your help. I'm
wondering why it changed after a reboot. Norton has been on the computer for
a month. (I just bought this computer a month ago.)
 
Thanks for the feedback... Glad to hear its working...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Back
Top