404 when trying to connect via Remote Desktop Web Connection

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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

To answer your questions and pose some additional ones:
Have you forwarded TCP Port 80 (IIS) through your home router?
Yes

Does your home ISP block TCP Port 80 inbound?
Click to expand...
I don't think so... see my response to the next question.
Can you connect to the PC over your local LAN using the Web connection?
Click to expand...
No... this is how I've been trying to connect, via
http://192.168.1.100/tsweb/ Note that I can reach the screen that asks for
server and screen size (which pulls content from the host PC, so there's no
blocking of the ports, etc.). It's just that when I click Connect, I get a
404 page rather than the login screen for the host PC.
If
you can check the router for the proper port forwarding settings.
Click to expand...
I did; they're correct.
If you
can't check the PC to see if any personal firewall software is blocking TCP
Port 80.
Click to expand...
I also disabled all local firewall software as a precaution

Thanks for your help,
Erik
 
Hmmm...since I don't use IIS I am kind of winging it here...:-)

Is the IIS server PC and the PC you want to connect to with RDP the same PC?

If so when you get the default IIS RDP page do you simply click on the
"Connect" button? You should not input a server address in that case.

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

Problem solved -- I'm now able to connect to the host PC. I was missing a
file called connect.asp in my /tsweb/ directory on the host PC.

Thanks for your suggestions & patience!

-Erik
 
Back
Top