Question Locked

Remote Desktop Web

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

1- i have been using regular RDT for a long time, no problems. i am trying to use Remote Desktop Web, so that i have more flexibility and use less band width.
2- i have followed all of the set-up procedures including opening ports, windows firewall, and router port forwarding. and un-installed IIS, shutdown, re-booted, re-installed & reconfigured.
3- i cannot make the browser connect.
4- i have 3 ports opened and forwarding; 80, 3389 & and my own between 1000 & 65535 (yyyy)
5- i have tried to connect using the following IP's
http://xxx.xxx.xxx.xxx/tsweb
http://xxx.xxx.xxx.xxx:yyyy/tsweb
http://xxx.xxx.xxx.xxx:80/tsweb
http://xxx.xxx.xxx.xxx:3389/tsweb
also, all of the above with https://xxx...
to eliminate the web / internet component, i have tried from a LAN computer using internal IP 172.16.xxx.xxx/tsweb
172.16.xxx.xxx:yyy/tsweb
172.16.xxx.xxx:80/tsweb
172.16.xxx.xxx:3386/tsweb
Host is running XP prof w/ sp 3.
also had another person double check settings.
Still unable to make the connection.
what could be blocking connection via web to host?

8 replies

by aj

XP prof w/ sp 3
through the web.

by shasca

Your layout all seems in place from your original post. If you can access both PC's put this on each and try it out of the box.

(I think TSWEB will only connect across the web to a Terminal Server.) (Within the same domain it works fine. As would remote desktop)

http://www.uvnc.com/

by churdoo

Understand though, that tsweb doesn't use any less bandwidth and doesn't actually run inside of the browser. TSWEB merely installs an Activex tsclient if it's not already installed and then simply passes the IP or name of the computer you're connecting to, to the tsclient. The name or IP has to be resolvable/accessible directly to the client, in other words tsweb will not "proxy" a connection to a separate internal host, if that makes sense.

Do you even get to the Remote Desktop Web Connection page in your browser when you try to connect to http://.../tsweb?
If you don't even get the Remote Desktop Web Connection from external or internal client, then it's your IIS that's misconfigured. If you get the connection page, fill in the name/ip of your host but fails to connect, then can be either the name/IP is not resolvable/accessible to the client or the Activex control may not be installed on your client.

These instructions don't look bad if you haven't already seen this link:
http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

by aj

I agree, either IIS misconfigured or ActieX.
i have the directions from the attached link, and have followed them, also had another person double check, no luck.
my guess is the ActiveX is not installed, or functioning correctly, or perhaps an IE security issue? how do i check if ActiveX is installed and working properly?

by churdoo

The activex is not called upon yet at this point -- the activex control is not called upon until you fill in a server name and hit connect.

Are you creating the tsweb virtual directory off of the default website or some other website and/or some other port. Are you trying to make the tsweb virtual directory respond under https or just straight http? Is there anything else in or under your default website that you can use to confirm that the default website is responding properly?

by aj

tried both http & https with all port options.
not sure what, where or how to check "default website"

This discussion is closed to new replies.