Hello,
I had Remote Desktop Services Gateway server setup correctly and working, but while trying to remote into my computer recently it wouldn't let me. I logged on to the server and it is saying the certificate on the server is no longer configured. When I choose Import existing certificate and apply everything appears correct. I push ok and it takes me back to the gateway manager screen and it says certificate not configured. I have tried importing my trusted certificate several times and selecting a self issued one without success. The only thing I haven't done is create a new certificate.
I am using a Go Daddy Certificate.
I have gone into IIS and the correct certificate is working properly. I have verified that when I load the rdweb page that it is displaying a valid certificate.
What I am trying to do is use the remote web access page logging in with my credentials. I select 'my computer' which then uses the gateway server to redirect me to the broker server located on my remote desktop server which redirect me to my assigned hyper-V Windows 7 computer.
This process works from my physical Windows 7 PC located on the same network by choosing it from the start menu, but doesn't from the remote site using the rdweb page. Which I believe all points back to the certificate.
I'm wondering if a new update caused this?
I can't tell you when this happened because it is a test scenario which I don't use very often.
Thank you,
Walter
Walter
I had Remote Desktop Services Gateway server setup correctly and working, but while trying to remote into my computer recently it wouldn't let me. I logged on to the server and it is saying the certificate on the server is no longer configured. When I choose Import existing certificate and apply everything appears correct. I push ok and it takes me back to the gateway manager screen and it says certificate not configured. I have tried importing my trusted certificate several times and selecting a self issued one without success. The only thing I haven't done is create a new certificate.
I am using a Go Daddy Certificate.
I have gone into IIS and the correct certificate is working properly. I have verified that when I load the rdweb page that it is displaying a valid certificate.
What I am trying to do is use the remote web access page logging in with my credentials. I select 'my computer' which then uses the gateway server to redirect me to the broker server located on my remote desktop server which redirect me to my assigned hyper-V Windows 7 computer.
This process works from my physical Windows 7 PC located on the same network by choosing it from the start menu, but doesn't from the remote site using the rdweb page. Which I believe all points back to the certificate.
I'm wondering if a new update caused this?
I can't tell you when this happened because it is a test scenario which I don't use very often.
Thank you,
Walter
Walter