6 comments

• 

  Gadya

  4 years ago

  I find that trying the remote desktop over the internet, using the external webaddress/tsweb, I get the remote desktop web page, but when I enter the name or ip address of any device I want to control then it can't find it - even if the device to be controlled is the gateway itself! There is a variation in response depending on whether I identify the host by name or by IP address but either way it fails.
  I can however get the other web pages on this ICF gateway. Needless to say remote desktop works fine on my private local network!
  reply
• 

  Rajiv

  4 years ago

  I have to say this article is pretty inaccurate. First of all this will not allow you to remote desktop into your computer from a Mac, PocketPC, or even an alternate browser on windows such as Mozilla. Remote Desktop over web takes advantage of Microsoft ActiveX controls and pretty much installs the Remote Desktop client in a limited way. You are still bound by the same restrictions and it just avoids downloading the remote desktop desktop client and running the installer everywhere you go.
  
  Also on another note this will not let you access your computer remotely without you opening port 80 for the webpage and port 3389 for the actual remote desktop. Remote Desktop over the web does not proxy the remote desktop over HTTP and therefore even if the computer hosting the remote connection page is the one you are trying to connect to, you will not be able to without opening port 3389 and connecting to the external ip address.
  reply
• 

  qmchenry

  4 years ago

  The recipe reads accurately to me and delivers instructions appropriate to its title. Perhaps you were hoping for something else. The author lets you know that the connection will work with IE5. It is sad to have to fire up that browser when you have seen the light and moved on to another browser. If you want to use an arbitrary OS to connect to a remote host, VNC would be a better fit as there is an impressive list of clients available.
  
  Your information about the TCP ports to open in order to access the remote system behind a firewall is helpful. One of the toughest steps to do when using software remotely is digging through the docs to find what ports to open. But, yes, you must open TCP ports to access services behind a firewall. It's like a law of physics that can't be broken.
  reply
• 

  pcmd

  3 years ago

  Followed instructions, setup additional user, but can't access PC via IE6.x. the environment is 2 win XP-Pro PCs on LOCAL NW w/Linksys router to comcast. Set web Access up on wife's PC. 192.168.10.103/tsweb - nothing (cept MSN search site). User name is same as I use on my PC 192.168.10.107. I assumed that since I was going local I would not have to open a firewall port - but I even tried that tooooo - NO LUCK. all SPs & patches are installed no other firewalls - aNY SUGGESTIoNS
  
  tom
  reply
• 

  Liam

  6 months ago

  Good article - Thanks
  reply
• 

  WebMax

  1 month ago

  PCMD - Make sure the user has local admin rights. I have come across the same problem as you before and that was the cause for it.
  
  I remember showing a staff of mine this, he thought it was some sort of hack!
  reply