Remote Desktop Web Connection through router not working.

I had a similar thought but when I explained my Remoted Desktop problem to Comcast tech support, I was told that they were not blocking port 80.

Perhaps I do not understand what you mean by "established connections."  As mentioned above, I have been successful with Remote Desktop (port 3389) but unsuccessful with Remote Desktop Web Connection (tried port 80.. and later port 3390).  I'll add that I've also been able to configure my router from a remote location via an HTTP interface.  That would be a port 80 operation, yes?   So I'm not clear on how my ISP might be allowing some kinds of connections but not others.

No, that's probably not the problem then. Well I had a problem once where inbound NAT mappings weren't working over port 80 but were fine on other ports. This turned out to be the routers web-based config page interfering as it also uses port 80. I just configured the routers config page to listen on port 9980 and it worked fine.

When you changed the port to 3390, did you use http://ipaddress:3390 when testing?

Yes, I used http://ipaddress:3390/tsweb.      And I too think I was having a conflict with my router's web-based config page interfering, which is one reason why I tried port 3390.  (even tried 8019 too)    I turned off my router's remote configuration feature to be sure.  Still no luck.  I really really thought this would work when I tried the different ports.

You do have both 3389 and 80 forwarded?

Another thing to check is IP restrictions in IIS. Although the defaults are to allow all.

Both 3389 and 80 are forwarded.   The default IIS setting says "(All Unassigned)" if that's what you mean.

No there's an option to restrict access by IP address in the properties page, directory security tab.

I see.   Under "IP address and domain name restrictions."   The edit button, however, is greyed out.    I do know that I've never changed that setting, so I'm okay so long as the default setting is to allow all.

And if you mean under "Anonymous access.." I've set that to allow anonymous access.

I agree that is seems like the router.  I never thought to try to DMZ as I have a general paranoia about putting my whole box on the net even for a few seconds.  But I'm frustrated enough to give it a shot.  And I might have an old router.. I'll check.

Note:  I completely forgot that I'd installed Norton Antivirus with "File System Real Time Protection" running in the background.  I'll uninstall it and test things out again tonight or tomorrow.  Thanks much for all your suggestions thus far.

I uninstalled Norton and tried 3390 again.  Voila, it worked.   Thanks for reasking about firewalls and for all the suggestions, drev001.

No problem.

i had exactly the same problem as you. I downloaded the tsweb software and during the installation, i noticed that the default installation location on the server side is C:\Inetpub\wwwroot\TSWeb. In fact for the tsweb to work properly, it should be C:\WINDOWS\Web\TSWeb. So you need to point the installation directory to this location. After I did this is is working fine from the WAN side. You just need to use to use the default settings for setting up IIs and make sure that you have opened ports 80 and 3389 for forwarding to the correct computer on your LAN. You have to set up win xp pro with a log in password to be able to access RD either with the RD client in accessories/communications, or using the web browser. Let me know if this works. It sure worked for me!

I have had the same problem and i also needed to forward port 443 (https)