Re: Remote Desktop connecttion
- From: "Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 5 Jan 2007 11:57:01 -0600
"Todd" <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CAE5409C-F797-41B8-BB48-58E50B6529A1@xxxxxxxxxxxxxxxx
tried connecting from another computer in my house on the lan using the
private ip address of the host computer and it times out on the connection...
also... when trying to connect from the outside source... I should be using
the private ip address found in the cmd ipconfig/all section correct? not the
public ip address of the router
"Sooner Al [MVP]" wrote:
"Todd" <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:072A703C-BCFF-4CB5-A9ED-F7988BAD380B@xxxxxxxxxxxxxxxx
> oh and I signed on to canyouseeme.org and there says there's an error
> message
> trying to se that port for remote desktop and then shows what looks to > be
> the
> outside router ip address
>
Make sure that when you test at home from another PC on your local LAN that
you call using the private IP of the PC you want to connect to. Its not a
valid test if you use the public IP...
http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html
To properly test the public IP you need to be at a remote location.
If the canyouseeme test fails from the PC you want to access and the local
test, detailed above, passes then it comes down to a port forwarding issue
in the router or your running a firewall somewhere that is blocking TCP Port
3389 incoming.
--
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...
If you test over your local LAN and you can't connect then you have an issue on the PC you want to remote connect to. Check the windows firewall or any other software firewall you may be running on the PC to make sure TCP Port 3389 is open. There is a troubleshooting section on the page I pointed you to in an earlier reply. If your running a Cisco VPN client or NAV worm protection or OneCare Live those all may block incoming RDP requests if not configured correctly.
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
Again, when calling the home PC from a remote location like work, a friends house, etc use the *public IP* of the router. When testing over your home LAN use the *private IP* of the PC.
--
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...
.
- References:
- Re: Remote Desktop connecttion
- From: Sooner Al [MVP]
- Re: Remote Desktop connecttion
- From: Sooner Al [MVP]
- Re: Remote Desktop connecttion
- From: Sooner Al [MVP]
- Re: Remote Desktop connecttion
- Prev by Date: Re: Network DVD burner "is not accessible"
- Next by Date: netgear keyword blocking problem on yahoo
- Previous by thread: Re: Remote Desktop connecttion
- Next by thread: Re: Can't connect anymore to my wireless network
- Index(es):
Relevant Pages
|