getting remote desktop Web connection to work over another port

  • Thread starter Thread starter merkurboy
  • Start date Start date
M

merkurboy

Hi all,

So I've set up Remote Desktop Web Connection by installing
the needed items(IIS, etc). I have set the listening port
to be a port other than 80, by changing it in the Default
Web Site settings. Here's the problem. I'm able to
access the box via a web browser using
http://x.x.x.x:Y/tsweb where Y is the port number it's
listening on, however, once the access screen loads up and
I attempt to continue, I get nothing but an error. I've
tried doing this by specifying the server in the server
line and by leaving it blank, anyone else run into this
issue and found a resolution?

Scott Renna
 
By the way, I don't seem to have a connect.asp in my
inetpub/wwwroot folder....anyone else had this problem?
 
For this to work, you need to get TWO ports through the network between the
client machine and the remote host.

Your changed port 80 is one, of course, and you've licked that one.

The other is port 3389, TCP for the ActiveX control to talk to the remote
host machine.

This one can also be changed, but you do need two ports.

See the box at the top of this reference for the HTML needed to change the
RDP port.

http://www.remotenetworktechnology.com/ow.asp?Remote_Network_Home/TerminalServices/WebClient#h4

You also need to change the listening port on the host machine, either in
the router (if you have a router which can specify different external and
internal ports) or at the host itself via:

http://support.microsoft.com/default.aspx?scid=kb;en-us;306759

Remember that the host machine requires a reboot after the port is changed
in the registry.
 
Back
Top