I have a Windows 2008 R2 Web edition server.
Is there are way I can remote desktop connect entirely through a browser. Meaning if "Remote Desktop Connection" on my pc is blocked, I can still connect?
Old topic, but still a relevant question. As of this year, anyway, there are some options for someone who wants to use an in-browser RDP solution.
Guacamole provides "HTML5 Clientless Remote Desktop": This is intended to be set up on a third server to act as a tunnel and proxy, to allow a client computer to connect to a remote computer, without having to specially configure either the client or the remote computers. If you don't want to use an intermediate third server, I believe you can install Guacamole on the remote server you want to connect to (presuming it runs a webserver) and point it to localhost, then access that webpage from your client computer's browser (for example).
RemoteSpark is another good option. They have a paid service, but you can apparently just download their HTML file and set it up for your own personal use if you have the savvy (source). What I would do in this case is drop the HTML file in a webserver directory on the server I want to access (on HTTPS of course), set it to connect to localhost so that no packets have to be transferred offsite anywhere except out to the client computer, hardcode all the settings I want, and put it up behind a login page with some two-factor authentication (at least one of the two factors being image-based or some other non-text or single-use method), in order to thwart keyloggers on public or otherwise insecure computers.
If you have admin control over the remote computer and want to set up and micromanage the RDP itself, you can try, say, a combination of FreeRDP and FreeRDP-WebConnect.
I was kind of wrong first time, if you have no control over the server then you are still out of luck but if you can get admin access then you can install the 'remote desktop web connection' subcomponent of IIS's WWW service via control panel and then browse to http://whatever/tsweb
Your Web port's open? You could enable a SSH tunnel listening on port 80. Sure, you'd have to install it on Windows and probably have it listen on a different port. That's one quick hack of a solution. Proxy 3389 via a Web proxy.
To add to the above list of browser based RDP clients, you can also try Myrtille, an open source solution comparable to Guacamole, but running on Windows Servers. It works for both HTML4 and HTML5, useful if you have an old browser.
You mean the outgoing connection is blocked?If that is the case you could just setup the server to use a different port, or just use another tool altogether, like logmein or vnc.
If you have access to the servers to make configuration changes ( since you host the servers) then you can configure it so that you can access your servers via a web browser (preferably Internet Explorer since it's a Windows server) . When you connect via a web browser to your Windows server, the traffic uses Port 443. Most companies open ports 80 (http) and 443 (https). If a company uses a web proxy server, they also usually open ports 80 and 443 through the proxy server.
So if you find yourself working at a company which only allows web traffic through a proxy server, as long as they allow Port 443 then you still CAN access your Remote Desktop Servers via the web browser. This article shows you how to configure such an environment :
Old topic, but still a relevant question. As of this year, anyway, there are some options for someone who wants to use an in-browser RDP solution.
Guacamole provides "HTML5 Clientless Remote Desktop": This is intended to be set up on a third server to act as a tunnel and proxy, to allow a client computer to connect to a remote computer, without having to specially configure either the client or the remote computers. If you don't want to use an intermediate third server, I believe you can install Guacamole on the remote server you want to connect to (presuming it runs a webserver) and point it to localhost, then access that webpage from your client computer's browser (for example).
2X has a "Client for RDP/Remote Desktop for Google Chrome", which is a Chrome extension which does not require a third server.
RemoteSpark is another good option. They have a paid service, but you can apparently just download their HTML file and set it up for your own personal use if you have the savvy (source). What I would do in this case is drop the HTML file in a webserver directory on the server I want to access (on HTTPS of course), set it to connect to localhost so that no packets have to be transferred offsite anywhere except out to the client computer, hardcode all the settings I want, and put it up behind a login page with some two-factor authentication (at least one of the two factors being image-based or some other non-text or single-use method), in order to thwart keyloggers on public or otherwise insecure computers.
If you have admin control over the remote computer and want to set up and micromanage the RDP itself, you can try, say, a combination of FreeRDP and FreeRDP-WebConnect.
You can also look into Ericom's AccessNow, and CybeleSoft's ThinRDP, and of course Microsoft has provided a Remote Desktop Web Connection (also see) feature wrapped into their RDP solution since Windows XP.
No.................still no.I was kind of wrong first time, if you have no control over the server then you are still out of luck but if you can get admin access then you can install the 'remote desktop web connection' subcomponent of IIS's WWW service via control panel and then browse to http://whatever/tsweb
Try it and let us know ok.
Old Post I know but . . .
Windows Live Mesh was excellent for anyone reading this. It syncs your data across PCs but it has a hidden feature.
It has remote desktop capability that is accessible via devices.live.com
RD support of Mesh is required to be enabled first on the remote machine, and as far as I know a HTTPS tunnel is created (443)??
Perhaps use a service like Logmein.com ... It uses port 80, so it should burrow through most anything.......
Your Web port's open? You could enable a SSH tunnel listening on port 80. Sure, you'd have to install it on Windows and probably have it listen on a different port. That's one quick hack of a solution. Proxy 3389 via a Web proxy.
You can try this, I use this with my AWS EC2 instances.
http://windows.microsoft.com/en-us/windows-vista/connect-to-another-computer-using-remote-desktop-web-connection "You can use Remote Desktop Web Connection to connect to a remote computer over the Internet. To do this, the remote computer must be running Windows Server 2008, and Terminal Services Web Access (TS Web Access) must be installed. "
To add to the above list of browser based RDP clients, you can also try Myrtille, an open source solution comparable to Guacamole, but running on Windows Servers. It works for both HTML4 and HTML5, useful if you have an old browser.
You mean the outgoing connection is blocked?If that is the case you could just setup the server to use a different port, or just use another tool altogether, like logmein or vnc.
Jim
If you have access to the servers to make configuration changes ( since you host the servers) then you can configure it so that you can access your servers via a web browser (preferably Internet Explorer since it's a Windows server) . When you connect via a web browser to your Windows server, the traffic uses Port 443. Most companies open ports 80 (http) and 443 (https). If a company uses a web proxy server, they also usually open ports 80 and 443 through the proxy server.
So if you find yourself working at a company which only allows web traffic through a proxy server, as long as they allow Port 443 then you still CAN access your Remote Desktop Servers via the web browser. This article shows you how to configure such an environment :
http://sengstar2005.hubpages.com/hub/How-to-Remote-Desktop-to-a-Terminal-Server-via-a-Web-Proxy