For Remote Desktop Web Connection [RDWC] you need both TCP Port 80 (IIS) and
TCP Port 3389 (Remote Desktop) forwarded through any router and/or firewall
the Remote Desktop [RDC] host/server PC is behind. Note that many ISPs
(including my own, Cox HSI) block TCP Port 80 incoming on residential
accounts. You can test this by going to the http://www.canyouseeme.org site
while on the host PC and test for both 80 and 3389. Also check with your ISP
about 80. If the ports are open and the test passes call from a remote
location using the public IP of your router.

Any reason you just don't use the regular (non-web based) RDC connection?

General RDC help...

http://theillustratednetwork.mvps.or...eshooting.html

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

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

"Suthagar" <Suthagar@discussions.microsoft.com> wrote in message
news:BAD414CF-3829-4842-829F-BC6670C8C38A@microsoft.com...
>I have setup remote Desktop Web Connection on my Desktop which has Windows
>XP
> Pro SP2. I have a laptop which has Windows XP Home Edition.I manage to
> setup
> network between Desktop and laptop wire wireless router. And I am able to
> connect my Desktop via RDWC. When I move my laptop to different ISP and
> connect via RDWB, it does not work.
>
> RDWC only works on same ISP, I think. Can anyone help me? What setup do I
> need in order to connect my desktop with different ISP?