astorrs wrote: » It makes use of HTTPS like you said, but it's more than just access to the one server. Using the 6.x version of the RDP client you give it the address of the TS Gateway on the Advanced tab and enter all the other credentials/servername as normal and it proxies the connection through the TS Gateway server directly to the server you are trying to connect to. The other computer sees the traffic as coming from the TS Gateway so you don't have to relax security, etc. to use it. I use it at home so I can remotely connect to my ESX environment from anywhere in the world without RDPing into something first.
mr2nut wrote: » Ahhh, I get the use for it now. For example, if I set up a port in my router to point port 3389 at a specific Server, you then can't create another rule to point the same port at another Server (obviously!) So RDP 6 essentially gives you a 'gateway' Server (as per the name) and then the front page of RDP to type the local IP/hostname of the Server you need. Fair does, think i'll have to set this up tomorrow. Cheers for that
mr2nut wrote: » Ive got it installed fine and working on the lan but he you could forward that info on to take a look at anyway id appreciate it man.
astorrs wrote: » If you've got it working and certificates issued, etc you should be fine. There were a few blog posts/articles I had saved that covered setup/config (which you seem to be past).
