Re: 404 when trying to connect via Remote Desktop Web Connection

Any network that blocks TCP Port 3389 outbound or inbound will break Remote
Desktop (RDP) and Remote Desktop Web connection. The Web connection uses
both TCP Port 80 (IIS) and TCP Port 3389 (RDP).

Have you forwarded TCP Port 80 (IIS) through your home router?
Does your home ISP block TCP Port 80 inbound?
Can you connect to the PC over your local LAN using the Web connection? If
you can check the router for the proper port forwarding settings. If you
can't check the PC to see if any personal firewall software is blocking TCP
Port 80.

--
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...


"Erik_In_Carlsbad" <ErikInCarlsbad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C312F936-3188-45DF-9AF1-7B6AA692A587@xxxxxxxxxxxxxxxx
Thank you for the response, Al.

I've kept IIS running over Port 80. I can remote desktop to the host
computer via the Remote Desktop software without a problem (from networks
that don't have any blocked ports --attempts to connect from places that
have
Port 3389 blocked don't work). Over my local network, I have no trouble
connecting via the Remote Desktop program to the host PC, nor over the
internet using the xxxxx.no-ip.info address.

The problem is with attempting to connect using the Remote Desktop Web
Connection. I can reach the host PC at xxxxx.no-ip.info/tsweb/ -- just
after
clicking "connect" I get a 404 page.

As an aside, I connected to another host computer using Remote Desktop Web
Connection and was able to reach that computer's login page. It also
prompted me to install the ActiveX control for Remote Desktop Web
Connection
-- something that never happened when attempting to connect to my host
computer.

Thanks for your help... I would appreciate any guidance you can offer to
get
me accessing my host PC via Web Access!

-Erik

"Sooner Al [MVP]" wrote:

First the Tsweb connection needs both TCP Port 80 (IIS) and TCP Port 3389
(RDP). Both must not be blocked outbound at work and inbound at home. If
they are you need to change one or the other port, ie. which ever one is
blocked.

With that said you could use something like Secure Shell (SSH) which uses
TCP Port 22 (or whatever you set it to) to access your home LAN then run
Remote Desktop through that or use something like SSL-Explorer to do the
same thing. SSL-Explorer uses TCP Port 443 and provides native support
for
Remote Desktop if your running a Java based copy of Internet Explorer.

The bottom line though is your office is blocking outbound ports for a
reason. I would pay a visit with the network admins to see if you are
truly
authorized to connect a trusted network (your office) to an untrusted
network (your home).

--
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...


"Erik_In_Carlsbad" <ErikInCarlsbad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:FCA196A3-5E55-41B1-A2D5-65255A4BA2D4@xxxxxxxxxxxxxxxx
I'm trying to set up Remote Desktop Web Conneciton on my home computer
so
that I can access my desktop using a web browser via TSWEB. I've been
accessing the computer for some time using the Remote Desktop client
without
a problem (host computer runs XP Professional, and I use a cable modem
and
a
no-ip domain to handle the dynamic IP addressing). I'm needing the web
access
because my job site blocks Port 3389.

I followed the steps in Tony Northrup's article "Set Up Remote Desktop
Web
Conneciton with Windows XP" (
http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx
). I can get to a Windows Remote Desktop Web Connection screen on the
host
PC (the one that requests server name and screen size). When I click
Connect,
however, I get a HTTP 404 - File not found / Internet Information
Services
error and I'm never able to reach a login page that requests my
username
and
password.

I would appreciate any suggestions you would have or whether this
question
should be posted to another group.

Thanks,
Erik





.

Relevant Pages

  • Re: Using Remote Desktop From an SBS Domain
    ... Internet connection, bypassing my SBS/ISA network all together. ... end of a Remote Desktop connection and have found little about it. ... the port number you connect to from 80 to a port of your ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Office to Home PC
    ... > permanent DSL Connection and a DynamicDNS Account) - IT WORKS from ... then why can I connect to my home-router through the same port ... > Essentially - you just said you have a home router (assuming cable ... > Remote Desktop port) by ways of a Remote Desktop Client. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Web Connection with Windows XP
    ... 1374, with the port opened. ... When I type in my home IP, how will Remote Desktop Web Connection know to ... ip) http://192.168.1.120:1374/tsweb/ but how do i enter the network ip ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Connection not working
    ... find the home server computer on Remote Desktop Connection. ... TCP Port 3389 inbound to your home connection. ... I do not have a router between the Dsl modem/router. ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: Re: Remote connections
    ... then installs the RDP activeX control and runs it in your browser, ... actual RDP connection still takes place over port 3389 and is not ... Aside from creating a VPN tunnel and then performing a Remote Desktop ... Aparently there is a Remote Desktop Web Connection feature that can be ...
    (Focus-Microsoft)