WinXP Remote Desktop

[MoFunk]

I am trying to help a friend set up remote desktop to his WinXP Pro machine to allow him to access from the web. I have followed the instructions from this page http://www.microsoft.com/windowsxp/expertzone/columns/northrup/03may16.asp and everything works until I hit connect at the tsweb page. I get a page cannot be displayed. We can access that box remotly on his lan from another XP machine, just not over the net. We changed his default web port and can see his webpage. We have set up port 3389 to forward to the ip of his web server. So when we go to http://user.dyndns.org: port#/tsweb we can see the login page, we hit connect and we get a page not found. Is there something I am overlooking? Thanks.

Had to put a space between the : port to avoid this

 

[EvilWobbles]

Do you have both port 3389 and whatever port you selected for TSWeb forward to the IP address of his WinXP Pro machine?

 

[SNC]

How is the client setup? Is it using MSTSC or the IE interface? I can see where using port redirects could be a problem after the initial request. I will configure a like setup and test it. See what I come up with.
Check to make sure you can connect with out using the dynamic DNS service.
If the problem is a dynamic IP address, just ping the dyndns name and then use the IP for TS.

 

[SNC]

If you are using the web server addin you should be using port 1374 not 3389.
Just a question. Why not just use TS outside of IIS?

 

[MoFunk]

Thanks guys. I doing this on mine and then I did something to freak the router out and I have to wait until I get home to restart it. Anyway port 3389 has been forwarded as well as the port we have the web host on. So we can see his webpage when we try. I was initially trying to set this up so he can use IE, that way if he is on the road and is able to get to a pc, he would not have to deal with loading MSTSC. I never thought to ping and use the IP, the thing that confuses me about that is we are able to see the first tsweb page, but then again that could be the hang up. When I can get the router going I will try again. Thanks.

 

[MoFunk]

Thanks SNC, I will try that other port. The article only mentions to open the port you are using for web and then 3389. Also your question, are you meaning just use a TS client software loaded and get in that way? If so, we can do if he is using his laptop, but he is concerned with if he is out and about and wants to get in, then he can find an internet cafe or whatever and do it that way. I also think he wants extra "geek" points when he shows it off to people. I may start using this method myself because at the moment I use pcanywhere which is fine when I am at work. But there are times I am at my Dad's house and want to look at something and it would be nice to be able to pop right in.

 

[SNC]

OK. I re-read the instructions. You need to forward port 3389 and the port you set IIS up to listen to. (the instructions use 1374 as an example) If you did not change anything, it should be 80. If you set it to use 3389 that would be a problem. Only one service can listen on one port. Make sure to set IIS to listen for web requests on a port other than 3389. What might be happening is that IIS is listing on 3389 as soon as you atempt to logon TS starts receiving requests on 3389 and killing IIS. Geek points are worth an extra week of work on a problem. I still havent been able to reproduce your problem. I cant afford to change the port IIS listens to. With my luck someone would need a file, and be sh!t out of luck.
Please let me know if this helps.

 

[MoFunk]

I can connect great using TSC, but not the web. When I click connect I get a file not found error. I also get this in the url http://*******.dyndns.org/tsweb/connect.asp?Server=*********.dyndns.org&rW=1024&rH=768& so does this mean it is looking for a connect.asp file? If so, how do I know that I have it on my system. I did a search for connect in the inetpub directory and found nothing.

 

[Wolf00]

it looks like the URL for the connect.asp isn't including the port number for your ISS server. I'm not quite sure why. You might try taking the URL you just posted and adding in the port number for your IIS server and see if that works so it looks something like this:

http://*******.dyndns.org:1234/tsweb/connect.asp?Server=*********.dyndns.org&rW=1024&rH=768&

Also, you may want to try using the inside IP address in the server portion (when you get to the initial page and you have to type in what server you're connecting to, use the private IP address). I setup my remote desktop using IIS a while back and I remember using the inside IP address because I was using the web interface for multiple computers on the same private network.

Hope this helps