The one you want to connect to. On Fri, Sep 9, 2011 at 5:17 PM, Neil Standley <n...@net-venture.com> wrote: > Hi Richard, > > Under the advanced tab I have selected "use these RD Gateway server settings" > > The server name matches the common name in the certificate I > purchased/installed on the server. It's a standard SSL cert (no wildcard). > Logon method (ask for password NTLM) > Bypass RD Gateway server for local addresses (is checked) > > > On the general tab for computer name, should I be using the name of the RD > Gateway server or the computer I want to connect to? > > Thanks, > Neil > > > -----Original Message----- > From: Richard Stovall [mailto:rich...@gmail.com] > Sent: Friday, September 09, 2011 12:40 PM > To: NT System Admin Issues > Subject: Re: TS Gateway questions > > It sounds like you haven't configured the client to actually use RDP over > HTTPS. > > Open the RDP client. If the tabs for General, Display, etc. are not showing, > click options. Go to the advanced tab and click settings in the connect from > anywhere section. Tick the radio button for use these RD gateway settings > and configure the appropriate values. > > That should get you going, I think. > > Did you buy a wildcart cert for this? If so, there are a few requirements on > the client side. The RDP clients in XP SP3, Vista SP1, and all flavors of 7 > support wildcart SSL certs natively, I believe. If your client isn't in that > list you may have trouble with a wildcard cert. > > On Fri, Sep 9, 2011 at 1:15 PM, Neil Standley <n...@net-venture.com> wrote: >> I’m setting up a TS Gateway server (2k8 R2, SP1 not installed yet) so >> my customer can remote to their workstations from home. I’ve followed >> the Technet guide to installing and configuring the TS Gateway role >> and have obtained/installed a CA signed SSL cert from Godaddy. >> >> >> >> In the TS Gateway manager under SSL Certificate it shows “The >> following certificate is installed on “ServerDC2” and lists the proper >> certificate (CA signed). >> >> >> >> However, when I connect to the server using an RDP client it displays >> a warning that the cert is not trusted. The common name in the cert >> warning is the old server (self signed) cert. >> >> I’ve restarted all of the TS Gateway services, but I haven’t rebooted. >> HTTPS and RDP (3389) are open on their firewall. >> >> >> >> Thoughts, suggestions? >> >> >> >> >> >> Thank you. >> >> Neil >> >> >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ >> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to listmana...@lyris.sunbeltsoftware.com >> with the body: unsubscribe ntsysadmin > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin
~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
