WS2008: Terminal Services Gateway Overview

Microsoft IT Professional Blog » The Performance Team Countdown

Microsoft IT Professional Blog » The Performance Team Countdown — Tue, 26 Feb 2008 21:35:30 GMT

PingBack from http://www.msitproblog.com/2008/02/25/the-performance-team-countdown/

re: WS2008: Terminal Services Gateway Overview

Steve — Thu, 05 Feb 2009 19:49:50 GMT

Is it possible to change the SSL port TS Gateway uses? I would rather use port 444 instead of 443.

Thanks.

re: WS2008: Terminal Services Gateway Overview

R Matthew Songer — Thu, 12 Feb 2009 00:00:08 GMT

I have a Windows XP Pro sp2 who had been connecting via VPN and RDC 5.1 to a remote site from inside our corporate network. The remote site has implemented a TS gateway. I upgraded the remote desktop software to v6.0. The user's profile on that machine cannot connect to the remote computer. The error is "The computer can’t connect to the remote computer because the certificate authority that generated the Terminal Server Gateway server’s certificate is not valid." I get this error after entering the logon credentials for the remote computer and the TSGW.

I can logon to the user's machine, browse to the RDP file in her profile and connect just fine.

I can set the user up on another machine that has never used RDC and connect just fine.

What file or setting could cause this behavior?

re: WS2008: Terminal Services Gateway Overview

Sean Constantine — Fri, 20 Mar 2009 12:12:04 GMT

I have read on other forums that it is not possible to change the TCP port listener for the TS Gateway, but have not found a MS KB or tech article. Further proof of this may be the RDC client does not seem to offer an obvious option to redirect TS gateway settings to a specific port.

I am researching this similar question as I would like to run Exchange OLAnywhere and TS Gateway services from a single IP (yes, my lame residential internet circuit). The only solution I have found unfortunately is to run both services on the same server (additional configurations are necessary to keep Exchange from rewriting the RPC proxy configuration).

re: WS2008: Terminal Services Gateway Overview

Eugene Borisov — Wed, 01 Apr 2009 23:43:06 GMT

Hello,

I am evaluating W2008 Terminal Server. In my case I have stand alone TS server sitting in DMZ zone. My AD domain controller and all other resources sit inside the perimeter. All needed ports, like RDP, LDAP, DNS, Radius are open for TS Gateway machine to internal LAN.

Now, this setup is not working for me. I have configured single policy with Central Network Policy Server pointing to my existing RADIUS server running on my AD DC server. No other policies exist on TS Gateway. When I attempt to make a remote connec tion using my domain account, I get denied access to TS. System event indicates "Uknown user or bad password". My RADIUS server works well for old VPN connections.

My question: is it possible to use TS Gateway on stand alone machine and still be able to use AD accounts to connect?

Thank you

re: WS2008: Terminal Services Gateway Overview

Ray — Wed, 06 May 2009 07:22:24 GMT

Could you cover off very simply the DNS / Naming / Cert requirements.

I'm having trouble understanding what to put where.

I have a pulblic free dynamic dns address URL and IP.

Do I need to insert the IP from my router to the Dynamic Hoster?

What name do I give the certificate - the name of the public URL address or the computer name?

Could you address these.

Thanks

raymond.scott@live.com