TS Gateway?

[Guest Ian Boyd]

From an external site, i want to Remote Desktop to a machine on the

workplace LAN.

 

i cannot VPN to the workplace because the the local router, like almost all

routers, cannot handle more than one Microsoft PPTP VPN connection. (Either

that or they just don't allow it - pick'em).

 

 

So what would be idea is a way to have Remote Desktop client software have

the ability to connect to a "proxy" or "gateway" computer that i can expose

to the Internets, and then that machine can forward the RDP traffic to the

desired machine on the local LAN. It would need to be on port 80 (HTTP), or

if really need be port 445 (HTTPS, with no valid certificate).

 

 

Spelunking through undocumented things, i see an option in the client

software: "Connect From Anywhere", where i can "configure Terminal Services

Gateway settings to connect to remote computers behind firewalls." Which

sounds like exactly what i want. But the going to my 2k3 server machine, and

going to Start->Help->"TS Gateway" yields no mention of any such technology.

 

Does such a technology exist, and if so how do i enable it on a server, and

where in the help files in the documentation for it?

[Guest Ian Boyd]

Re: TS Gateway?

 

Here is the Microsoft page talking about TS Gateway. All it gives are error

codes:

http://technet2.microsoft.com/windowsserver2008/en/library/c7ddc4e9-1316-4759-915f-47245fe4d12e1033.mspx?mfr=true

 

Here's KB Article describing how RDP6 supports TS Gateways:

http://support.microsoft.com/kb/925876

 

Here's a blog entry on MSDN saying how much TS Gateway on Vista server

rocks:

http://blogs.msdn.com/david.wang/archive/2006/07/27/TS-Gateway-on-Vista-Server-Rocks.aspx

 

Here's a page on Microsoft telling you what a TS Gateway is:

http://windowshelp.microsoft.com/Windows/en-US/Help/011fcc70-fdb7-43fc-ae08-b33169b3f6961033.mspx

 

Here's a forum post saying that the new RDP6 client will support TS

Gateways:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=455646&SiteID=17

 

Here's a blog entry from the Terminal Services team on how to setup TS

Gateway in the client:

http://blogs.msdn.com/ts/archive/2007/05/04/single-credential-prompt-for-ts-gateway-server-and-terminal-server.aspx

 

 

And so on.

 

All that's missing is the most important part - the TS Gateway.

[Guest TP]

Re: TS Gateway?

 

TS Gateway is a feature of Windows Server 2008. You

can try the release candidate if you want:

 

http://www.microsoft.com/windowsserver2008/audsel.mspx

 

-TP

 

Ian Boyd wrote:

> From an external site, i want to Remote Desktop to a machine on the

> workplace LAN.

>

> i cannot VPN to the workplace because the the local router, like

> almost all routers, cannot handle more than one Microsoft PPTP VPN

> connection. (Either that or they just don't allow it - pick'em).

>

>

> So what would be idea is a way to have Remote Desktop client software

> have the ability to connect to a "proxy" or "gateway" computer that i

> can expose to the Internets, and then that machine can forward the

> RDP traffic to the desired machine on the local LAN. It would need to

> be on port 80 (HTTP), or if really need be port 445 (HTTPS, with no

> valid certificate).

>

>

> Spelunking through undocumented things, i see an option in the client

> software: "Connect From Anywhere", where i can "configure Terminal

> Services Gateway settings to connect to remote computers behind

> firewalls." Which sounds like exactly what i want. But the going to

> my 2k3 server machine, and going to Start->Help->"TS Gateway" yields

> no mention of any such technology.

>

> Does such a technology exist, and if so how do i enable it on a

> server, and where in the help files in the documentation for it?

[Guest Ian Boyd]

Re: TS Gateway?

 

> TS Gateway is a feature of Windows Server 2008.

 

The feature in the existing client cannot be used on an existing server?

[Guest TP]

Re: TS Gateway?

 

TS Gateway is new feature of Windows Server 2008, it

is *not* a feature of Windows Server 2003, Windows

Server 2000, or NT Terminal Server Edition.

 

The version 6 client exists primarily for connecting to

Windows Vista and Windows Server 2008. I don't

recommend it because it has bugs and is slow. Much

better to use the 5.2.3790.x version *unless* there is a

specific new feature you need (like RemoteApp or TS

Gateway if connecting to 2008).

 

-TP

 

Ian Boyd wrote:

>> TS Gateway is a feature of Windows Server 2008.

>

> The feature in the existing client cannot be used on an existing

> server?