Remote Desktop w/IP address

Thanks for the response. I tried from a remote location and had the same
result. (same error message too) using Remote Desktop. When I tried the
/tsweb version from MSIE, I got a "server not found" message as well.

I should note that my home IP is not ping-able from the remote location
either.

What's strange, is that I am able run a streaming session using Windows
Media Encoder that even through my router, my friend could connect to using
the public IP address. Even though ipconfig would still give me the internal
ip address from the router, he could still connect by using the public ip
plus a port number to my windows encoder session.

I'd much rather use Remote Desktop than some third party app.

Thanks!!


"Sooner Al [MVP]" wrote:

> "JR" <JR.RemoveThis@discussions.microsoft.com> wrote in message
> news:5D1FA48F-1587-401D-A233-F769AB112EF9@microsoft.com...
> >I have two computers, both running XP Pro. Using my home network, I can do
> > remote desktop between my laptop (client) and my desktop (host).
> > Everything
> > works perfectly.
> >
> > However, I'd like to be able to use my laptop to access my home computer
> > via
> > the computer's IP address.
> >
> > I have a router. That means when I type ipconfig, it gives me the
> > internal
> > network ip address, not the real one. I can go into the router (or
> > whatismyip.com) and see what my real static IP address is. (Also, I made
> > sure to go into the router's setup and forward port 3389).
> >
> > So...on my laptop, I run Remote Desktop, and type in the IP address, the
> > same login and password...and it gives me an error message.
> >
> > The Client could not connect to the remote computer. remote connections
> > might not be enabled or the computer might be too busy...etc
> >
> > I know it's not any of those things because I can do it by typing the
> > computer's name on my home network.
> >
> > One thing that bothers me...is that I'm typing in the IP address while my
> > laptop is connected to the same router. Would this cause it not to work?
> >
> > I do not want to do the "Web Remote Desktop" I just want the standard
> > connection. I'd only be connecting with my own laptop.
> >
> > Thanks!
>
> To test using the public IP of the router, ie. the IP assigned by your ISP,
> you must be at a remote location. Its generally not a valid test to call one
> PC from another PC on your local LAN using the public IP. Many consumer
> grade routers do not support that "loopback" functionality.
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDia...ms/Basi
>
> See this page for additional help, hints, tips, etc...
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetup...Trouble
>
> Post back if you have additional questions...
>
> Good luck...
>
> --
>
> 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...
> How to ask a question
> http://support.microsoft.com/KB/555375
>

"JR" <JR.TakeThisOut@discussions.microsoft.com> wrote in message
news:86BF81F9-5E30-42AC-AFE1-4A6A21C10A7A@microsoft.com...
>
> Thanks for the response. I tried from a remote location and had the same
> result. (same error message too) using Remote Desktop. When I tried the
> /tsweb version from MSIE, I got a "server not found" message as well.
>
> I should note that my home IP is not ping-able from the remote location
> either.
>
> What's strange, is that I am able run a streaming session using Windows
> Media Encoder that even through my router, my friend could connect to
> using
> the public IP address. Even though ipconfig would still give me the
> internal
> ip address from the router, he could still connect by using the public ip
> plus a port number to my windows encoder session.
>
> I'd much rather use Remote Desktop than some third party app.
>
> Thanks!!
>
>
From the desktop PC what happens if you go to the http://www.canyouseeme.org
site and run the test for port 3389?

If it passes you have port forwarding correct in the router. If it fails
either port forwarding is not setup correctly or your ISP is blocking
incoming traffic on port 3389 (unlikely but possible) or you have a firewall
blocking incoming Remote Desktop requests from the public internet.

Are you running a software firewall on the desktop PC that may be blocking
incoming Remote Desktop requests from the public internet but not the local
network? See this page for help checking the Windows Firewall. Make sure the
address scope for Remote Desktop is set for "Any computer (including those
on the internet"...

The web based method will fail if...

1. You don't have IIS running and configured for Remote Desktop.
2. You don't have both TCP Port 80 (IIS) and TCP Port 3389 (Remote Desktop)
forwarded through your router.
3. Your ISP blocks TCP Port 80 because running a web server on a residential
account may violate the terms of service.

Generally, but not always, pinging your router will fail because of a
configurable in the router which disables that...
--

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...
How to ask a question
http://support.microsoft.com/KB/555375

"Sooner Al [MVP]" <SoonerAl DeleteThis @somewhere.net.invalid> wrote in message
news:61497D09-EAC0-4F82-8215-760EADD5C77B@microsoft.com...
> "JR" <JR DeleteThis @discussions.microsoft.com> wrote in message
> news:86BF81F9-5E30-42AC-AFE1-4A6A21C10A7A@microsoft.com...
>>
>> Thanks for the response. I tried from a remote location and had the same
>> result. (same error message too) using Remote Desktop. When I tried the
>> /tsweb version from MSIE, I got a "server not found" message as well.
>>
>> I should note that my home IP is not ping-able from the remote location
>> either.
>>
>> What's strange, is that I am able run a streaming session using Windows
>> Media Encoder that even through my router, my friend could connect to
>> using
>> the public IP address. Even though ipconfig would still give me the
>> internal
>> ip address from the router, he could still connect by using the public ip
>> plus a port number to my windows encoder session.
>>
>> I'd much rather use Remote Desktop than some third party app.
>>
>> Thanks!!
>>
>>
> From the desktop PC what happens if you go to the
> http://www.canyouseeme.org site and run the test for port 3389?
>
> If it passes you have port forwarding correct in the router. If it fails
> either port forwarding is not setup correctly or your ISP is blocking
> incoming traffic on port 3389 (unlikely but possible) or you have a
> firewall blocking incoming Remote Desktop requests from the public
> internet.
>
> Are you running a software firewall on the desktop PC that may be blocking
> incoming Remote Desktop requests from the public internet but not the
> local network? See this page for help checking the Windows Firewall. Make
> sure the address scope for Remote Desktop is set for "Any computer
> (including those on the internet"...
>
> The web based method will fail if...
>
> 1. You don't have IIS running and configured for Remote Desktop.
> 2. You don't have both TCP Port 80 (IIS) and TCP Port 3389 (Remote
> Desktop) forwarded through your router.
> 3. Your ISP blocks TCP Port 80 because running a web server on a
> residential account may violate the terms of service.
>
> Generally, but not always, pinging your router will fail because of a
> configurable in the router which disables that...
> --
>
> 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...
> How to ask a question
> http://support.microsoft.com/KB/555375
>

I forgot to ask...

Is this a cable ISP like Comcast/Cox or are you on a DSL ISP like Verizon?
If its the latter, ie. DSL, then its possible your DSL modem is also a
router and either needs to be put in a pass through or bridge mode or
configured to forwarded TCP Port 3389 traffic to your router.

--

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...
How to ask a question
http://support.microsoft.com/KB/555375

The 3389 port is forwarded, but when I tested it with canyouseeme.com it
said it couldn't see the service. Reason: connection refused. I assume I
only have to open the TCP Port 3389 and not UDP as well?

I have Comcast broadband.

Thanks for the replies. Is there a way to configure Remote Desktop to use
another port if that becomes necessary?

"JR" <JR.RemoveThis@discussions.microsoft.com> wrote in message
news:1581BA60-9881-418A-A076-E0A70C233042@microsoft.com...
>
> The 3389 port is forwarded, but when I tested it with canyouseeme.com it
> said it couldn't see the service. Reason: connection refused. I assume I
> only have to open the TCP Port 3389 and not UDP as well?
>
> I have Comcast broadband.
>
> Thanks for the replies. Is there a way to configure Remote Desktop to use
> another port if that becomes necessary?

If the test on www.canyouseeme.org fails then you have an issue with the
router or a firewall somewhere blocking incoming Remote Desktop (RDP)
requests.

*Have you tried resetting the router?
*Are you running any software firewall on the desktop that may be blocking
requests from the public internet versus the local LAN?
*Are you running anything like NAV or OneCare Live that may be blocking
requests from the public internet versus the local LAN? I have also seen
reports of a Cisco VPN client blocking incoming RDP requests...

You can use an alternate port if you want. Note you need to hack the
registry on the desktop RDP host then reboot that PC after the change.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306759

Addressing after the port change...

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304304

You only need TCP Port 3389. You don't need UDP Port 3389...

In any and all cases use a *STRONG* password...

--

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...
How to ask a question
http://support.microsoft.com/KB/555375