G
Guest
We wish to make a windows application available by use of terminal services
to customers. These customers will be from different companies, many of them
behind firewalls etc.
We want these clients to be able to connect to Terminal Services with
minimum logins, and setup (i.e no need to get their IT staff involved).
Currently we are trialling some setups. We have a windows 2003 server behind
our firewall, and ports 80, and 3389 are being forwarded to it. From a home
broadband connection, the RDP client works fine. But it appears that most
companies will not have port 3389 open to allow outbound RDP connections.
I then tried using the web RDP client. I setup the Web client on the windows
2003 server, and tried to get some people to connect to the website, install
the ActiveX RDP client, and still it would not connect. It appears the
ActiveX RDP client uses port 80 to simply connect to the website, but uses
3389 to talk on.
I tried changing port 3389 to all kinds of common open port numbers, eg. 21,
80.
However, many friends still could not connect on these port numbers, perhaps
the firewalls they are behind are filtering traffic through those ports, to
ensure it is FTP or HTTP traffic only.
So my question is, is there a general port available which will accomodate
Terminal Services connectivity? What is the easiest approach to deploying
such an application to our customers?
many thanks
rajah
to customers. These customers will be from different companies, many of them
behind firewalls etc.
We want these clients to be able to connect to Terminal Services with
minimum logins, and setup (i.e no need to get their IT staff involved).
Currently we are trialling some setups. We have a windows 2003 server behind
our firewall, and ports 80, and 3389 are being forwarded to it. From a home
broadband connection, the RDP client works fine. But it appears that most
companies will not have port 3389 open to allow outbound RDP connections.
I then tried using the web RDP client. I setup the Web client on the windows
2003 server, and tried to get some people to connect to the website, install
the ActiveX RDP client, and still it would not connect. It appears the
ActiveX RDP client uses port 80 to simply connect to the website, but uses
3389 to talk on.
I tried changing port 3389 to all kinds of common open port numbers, eg. 21,
80.
However, many friends still could not connect on these port numbers, perhaps
the firewalls they are behind are filtering traffic through those ports, to
ensure it is FTP or HTTP traffic only.
So my question is, is there a general port available which will accomodate
Terminal Services connectivity? What is the easiest approach to deploying
such an application to our customers?
many thanks
rajah