rds gateway and changed certificate

we have inherited a setup with a terminal server and a gateway, where the certificate is expired. We've deleted the old certificate and configured the new one.
But still - the old one is presented.
but why??

We can see that the server is installed with Win2012R2 but it seems that the old terminal services gateway is configured, not the RDS gateway in Win2012.
anyone?
LVL 23
Jakob DigranesSenior ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alex GreenProject Systems EngineerCommented:
It's probably still in IIS, load up IIS on the RDS gateway and look for it.

https://ryanmangansitblog.com/2013/08/07/configure-connect-to-a-remote-computer-in-rdweb-2012/

That may help

Regards
Alex
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jakob DigranesSenior ConsultantAuthor Commented:
OK ----- the error was rather freakish.
The customer have 2 different sites, with 2 different AD-forests.
* AD Forest 1 use Direct Access
* AD Forest 2 use Terminal Services and RD Gateway
* AD Forest 2 had TS Gateway (almost) fully configured
* AD Forest 1 had a TS Gateway setup collocated on a server with several other roles
* but still, Users access TS Server traversing from AD Forest 1 - via Site-2-Site VPN to AD Forest 2.

noticed this when I looked at IIS settings for TS Gateway in AD Forest 2 and noticed a spelling error. A new DNSLOOKUP resolved to a somewhat similar public IP with .2 rather than .122 at the end - which was terminated at firewall in AD Forest . Mostly luck - but the web page in the link put me on to this
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.