G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Hello All,
I am trying to use Microsoft Proxy Server 2.0's 'reverse proxy' feature
to allow access to Remote Desktop on an XP Pro machine behind the proxy
server.
To get this to work, I need to know the name of the executable on the
XP Pro machine that actually binds to port 3389. Once I know this, I
can create a wspcfg.ini file allowing the Winsock Proxy Client to bind
to port 3389 on the proxy server, enabling remote logins.
As an example, the following wspcfg.ini file allows NetMeetings
conf.exe to bind to the ports it needs:
[conf]
ServerBindTcpPorts=1503,1720,1731
UseProxyIpForGetHostByName=2
KillOldSession=1
This file is placed in the NetMeeting program directory, alonside
conf.exe.
To create a similar file for Remote Desktop, what is the executable
that actually binds to port 3389?
Thanks in advance,
- Adrian
Hello All,
I am trying to use Microsoft Proxy Server 2.0's 'reverse proxy' feature
to allow access to Remote Desktop on an XP Pro machine behind the proxy
server.
To get this to work, I need to know the name of the executable on the
XP Pro machine that actually binds to port 3389. Once I know this, I
can create a wspcfg.ini file allowing the Winsock Proxy Client to bind
to port 3389 on the proxy server, enabling remote logins.
As an example, the following wspcfg.ini file allows NetMeetings
conf.exe to bind to the ports it needs:
[conf]
ServerBindTcpPorts=1503,1720,1731
UseProxyIpForGetHostByName=2
KillOldSession=1
This file is placed in the NetMeeting program directory, alonside
conf.exe.
To create a similar file for Remote Desktop, what is the executable
that actually binds to port 3389?
Thanks in advance,
- Adrian