Alternate port for Remote Desktop Web Connection ActiveX control

Does anyone know how to, or if, the port for the Remote
Desktop Web Connection ActiveX control can be changed?

In order to enable unrestricted third party firewall
traversing for inbound connections from the internet, I
would like to enable connectivity to terminal services on
alternate, and generally open ports (80 or 443), rather
than the default 3389. In a test environment, I have
changed the pertinent settings on a W2K Terminal Server
(HKLM\System\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp), and can connect to it
successfully using the Remote Desktop Connection client
(Hostname:AlternatePort), but have not found a way to
connect with the ActiveX control using an alternate port.

As this is a configurable setting on the server side, one
would expect that all clients would have this capability
as well.

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

states:
NOTE: The Terminal Server ActiveX client listens on TCP port 3389
and this cannot be changed. The Remote Desktop Protocol (RDP)
client that is available in Microsoft Windows XP and Windows .NET
(version 5.1 and later) has this ability.

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

is valid only for Windows 2003 / XP SP1.

Have you tried with the latest client from
http://www.microsoft.com/downloads/...ilyID=e2ff8fb5-
97ff-47bc-bacc-92283b52b310&DisplayLang=en

--
Vera Noest
MCSE, CCEA, MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please answer in newsgroup ---

"DagS" <Dag.Sjolund@bestwestern.com> wrote in news:347e01c34008
$aea857d0$a601280a@phx.gbl:

> Does anyone know how to, or if, the port for the Remote
> Desktop Web Connection ActiveX control can be changed?
>
> In order to enable unrestricted third party firewall
> traversing for inbound connections from the internet, I
> would like to enable connectivity to terminal services on
> alternate, and generally open ports (80 or 443), rather
> than the default 3389. In a test environment, I have
> changed the pertinent settings on a W2K Terminal Server
> (HKLM\System\CurrentControlSet\Control\Terminal
> Server\WinStations\RDP-Tcp), and can connect to it
> successfully using the Remote Desktop Connection client
> (Hostname:AlternatePort), but have not found a way to
> connect with the ActiveX control using an alternate port.
>
> As this is a configurable setting on the server side, one
> would expect that all clients would have this capability
> as well.