Printable View
Hello all, I installed IIS and the ActiveX control for web connection on a server. I have remote desktop installed on some clients. If I am logged into the server, and goto http://<servers ip>/tsweb/, and then type in the ip address of the computer I want to connect to, it works. However, if I am 'outside' the network...and type in http://www.<static ip>.com/tsweb it brings up the remote connection screen....but it wont allow me to connect to anyone. Does anyone know what might be wrong?
I dont use that program, but sounds like you just need to port forward.
https: maybe...
www.<ip address>.com - wouldn't that really be https://xxx.xxx.xxx.xxx/tsweb?
At any rate RobDog has done this - I'll pm him to get into this thread for you.
It sounds like you just have remote desktop enabled on the server and are trying to connect to some pc's on the remote network? No Remote Web Workplace, correct?
Are you able to login remotely to the server?
What version of Windows Server are you running?
Rob:Quote:
Originally Posted by RobDog888
Yes, I have remote desktop enabled on all of the client pc's on the remote network. I also have it enabled on the server (running Windows 2003). I also have IIS and 'Remote Desktop Web Connections' running on the server. While out of the network, I can connect to the server via Web Connections (http://<servers external IP>/tsweb), but when I enter a clients name/ip in the textbox, and connect...I get 'The specified remote computer could not be found, Verify that you have typed the correct computer name or IP address, and then try connecting again.'.
However, if I use NORMAL Remote Desktop (the program)....and remote desktop to the server...then either open IE and goto http://localhost/tsweb, and connect to the client....or open remote desktop on the server...it allows me to connect.
To me, this sounds like a port forwarding problem...technically I would have say 10 pc's on that network...that i'd like to get remote access through, via the web connection version of Remote Desktop...and all 10 pc's (and the server) would be using port 3389, right?
Terminal Services uses 3389 and Remote Web Workplace uses 443. One other thing I noticed is that you are using http for external connectionstring. Shouldnt you be using https?
Rob:
"Remote Web Connection" and "Remote Web Workplace"...are they the same? What I see when I go to https://ipaddress/tsweb is this:
http://img.photobucket.com/albums/v4...eenShot026.jpg
In my firewall/router...I setup 443 to be allowed from anywhere externally to anywhere in the network..3389 also is allowed to the remote server im trying to access. It's just once connected to the server, I cant connect to desktops.
RWW is different from RDWC. Here is my thread on RWW when I was having issues setting it up on Small Business Server 2003.
http://vbforums.com/showthread.php?t=403684
Do you have a firewall? I think there is one more port needing to be forwarded and do the other systems allow external connections via their firewall policies (assuming all systems are XP).
I have a firewall (WatchGuard FireBox 1000). I have 443 allowed for everyone...I also have 3389 forwarding to the server. As for the other systems (yes, XP)...they all allow for connections.Quote:
Originally Posted by RobDog888
Can you check your firewall's log and see what is being blocked? (if anything)
I dont see anything in my logs, but I do know that this works if I am either physically at the server....or REMOTE DESKTOP (program, not web version) to the server...then open IE in the server...and connect to localhost/tsweb.