Seems way to complex LOL when I can just purchase an authoritative DNS firewall for a couple hundred buck and let that do the job for me :)
Jean-Paul Natola > Date: Mon, 13 Jan 2014 11:11:18 -0800 > From: [email protected] > To: [email protected] > Subject: Re: [NTSysADM] RDS Gateway and Connection question > > I believe ARRRRRRRR (application request routing) will be your friend here. > It's how we're getting OWA and RDgateway and all that stuff working on > Essentials. > > On 1/13/2014 8:36 AM, J- P wrote: > > > > > > We have been using Citrix XA for years, however, having 2012 and > > RDS/TS licenses i think I will be making to RDG question is > > > > If my firewall is configured to forward 443 (https) to my Exchange > > server, then how can i forward 443 to RDG? > > > > Am i overlooking something obvious? > > > > > > TIA > > > > > > > > > > > > > > > > > > > > > Date: Sun, 12 Jan 2014 22:15:14 -0800 > > > From: [email protected] > > > To: [email protected] > > > Subject: Re: [NTSysADM] RDS Gateway and Connection question > > > > > > No. You don't change 3389 on the server. In the RDP app you've > > > clicked on Advanced > > > and entered in the url of the RDgateway? > > > > > > You do put in the hostname of the computer in the computer field. > > > > > > So servername goes in the computer field and then rdgateway.domain.com > > > (or whatever the url is) for the Advanced tab section. > > > > > > On 1/12/2014 10:01 PM, Jimmy Tran wrote: > > > > So the RDgateway server is the RDhost I want to connect to. For > > the computer name, I've been putting the public hostname. Yes to the > > second part. > > > > > > > > I tried using the local hostname in the "computer" field but that > > didn't help. Do I need to change the listening port RDP port on the host? > > > > > > > > -----Original Message----- > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Susan Bradley > > > > Sent: Sunday, January 12, 2014 9:51 PM > > > > To: [email protected] > > > > Subject: Re: [NTSysADM] RDS Gateway and Connection question > > > > > > > > Yes it goes over 443. You've put in the name of the computer and > > then in the rdp connect from anywhere section you've entered in the > > url of the RDgateway server and checked "use my RDgateway credentials > > for the remote computer" yes? > > > > > > > > What do the log files say? > > > > On 1/12/2014 9:37 PM, Jimmy Tran wrote: > > > >> Hi All, > > > >> > > > >> I just setup my first RDS gateway and I'm having some trouble in the > > > >> configuration. The goal is to use port 443 and not 3389 for the > > > >> connection right? I've seem to have everything setup but when I close > > > >> the port 3389, my connection fails. When attempting to connect, I get > > > >> the gateway disclaimer but it fails right after that. It doesn't > > > >> connect until I open up 3389. In the Remote App Manager, I changed > > > >> that port to 443 and rebooted the server but I still cannot connect. > > > >> > > > >> Do I have to change the RDP listening port in the registry? > > > >> > > > >> Am I supposed to specify port 443 in the host name while connecting > > > >> via RDP? > > > >> > > > >> Any pointers are appreciated. > > > >> > > > >> Thanks, > > > >> > > > >> Jimmy > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > Got your CryptoLocker prevention in place? > http://www.thirdtier.net/2013/10/cryptolocker-prevention-kit-updates/ > > >
