Terminal Service client port and Web Client port.

[Joe M]

Hi, I am sure that to use Terminal service using remote desktop client
you'll need port 3389 open on the Cisco router. But I am not sure about the
Terminal Service Advanced client (Web Client), does the web client need port
3389 opened?? Can it just work on the http port 80/ or a nominated port??? I
need to Terminal Service into the office from another company, and the only
port 80 is open and available for use..
What port does web client operate upon???

 

[Vera Noest [MVP]]

You'll need to open up port 80 to your IIS server and port 3389 to
your terminal server.
After the initial connection with the IIS server for downloading of
the Active-X component and authentication, the IIS is not part of the
session anymore, and all traffic is over rdp between your client and
the TS, using port 3389.

 

[Joe M]

Can Remote desktop/ Remote Web client be configured to work on the http port
80??? Because I am behind a corporate firewall and the only port 80 is
available and open...thanks

 

[Vera Noest [MVP]]

You can change both the listening port for Terminal Services and
the port on the client. If it is a good idea to change these to
port 80, I am not sure. Note that changing the listening port for
TS will mean that *all* clients need to change port as well.

187623 - How to Change Terminal Server's Listening Port
http://support.microsoft.com/?kbid=187623

304304 - Configuring the Remote Desktop Client to Connect to a
Specific Port
http://support.microsoft.com/?kbid=304304

326945 - How to Change the Listening Port in the Windows Terminal
Server Web Client
http://support.microsoft.com/?kbid=326945