Hi all
Dodgy title, but I will try to explain the situation:
A customer has two network segments, one is without internet access. The other segment holds a terminalserver which has been configured with SSL-encryption on the RDP protocol. Public certificate delivered from a Trusted Provider. This is accessible from the internet.
There is a route to the terminal server from the segment without internet, and every time users tried to log in to the server there has been a delay before they got to the login screen. I guess this is because the machines without internet is trying to reach the next level in the certificate chain encrypting the RDP. So after the request times out they got to the server. See the past tense? They don't anymore..
It's been about a year where everything has been working nice - suddenly no one can log in anymore and I immediately suspect the SSL situation. From the outside everything works nicely - the cert has been renewed in good time and seems fine.
So how to remedy the situation? Is there any way to make clients trust the certificate without going the certificate chain way? Or maybe I should enable a route to this providers IP addresses?
Anyone with a clue? Tips much appreciated....