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, sounds like you have a cert issue to me too.

Have you tried to remove the cert entirely, reboot, then re-add the cert to the Personal Store (via MMC), then re-pick it using the "select an existing cert ...." option?

Also, do you see any red in your event logs that might halp us understand why it no longer likes this cert?

Hey Kristin,

I tried what you suggested, but it still does the same thing.   I tried uninstalling and reinstalling the remote gateway service and it seem to work for about 5 minutes and then it broke again.

I tried creating a certificate from my CA, issuing a self signed to itself and reimporting my trusted cert all with the same affect.

Event viewer only has one error message.   You have not configured a certificate.

I also never noticed before, but the webpage and everything else says the same thing certificate not configured properly.   So it is not really a guess as to what is wrong it definately is the cert.

I will continue to investigate, but it may just be a product of me doing so many test environments on the same box and they are conflicting with each other.   I do plan on reloading my servers to get them working in isolated labs so they don't affect me as much.  At the time I started all this I only had one Hyper-V server, so I was limited on what I can do.  I have a second server, so perhaps that'll make things easier.

For example that server is my Exchange 2010 Transport Server, Hyper V, DNS, DHCP, Remote Desktop Gateway Server, File Server, and Domain Controller.  It was working perfectly fine before, but I have had other servers I deployed and removed from the organization that maybe didn't remove properly.   Such as Windows Deployment services, a different CA, and a Office Communicator Server.

Anyways if you have any more ideas let me know.

Thank you,

Walter

Hi,

 

Based on your description, I understand that you can access the rdweb page internally without using RD Gateway. However, when you try to access the page from a remote site via the RD Gateway, it fails with the error message “no certificate was configured”. If there is anything I have misunderstood, please let me know.

 

I suggest that you install the hotfix KB976484 and check if it solves the issue:

 

You have problems when you try to connect to the Remote Desktop Gateway (RD Gateway) that is hosted on a computer that is running Windows Server 2008 R2

http://support.microsoft.com/kb/976484

Hey Joson,

Thank you for the reply.   You did misunderstand my issue.   The problem described in that support article prevents a person from accessing the IIS website completely.

I could access the site, but when trying to make a connection to any of my remote apps or remote desktop connection it would not work.   The article describes a hotfix which I don't think is necessary.   When that issue occured for me it was because Remote desktop Gateway server created a new HTTPS binding even though there was one already in there for Exchange.   As a result I had two 443 bindings to the same IP address.  Deleting one fixed the issue.

Anyways on the positive side you motivated me to try searching support articles which I found the following article:  http://support.microsoft.com/KB/959120

And as it said I deleted the binding that was set to use all unused addresses instead of the one that was set to a specific IP address.

The correct action would have been to do the opposite.  For remote desktop gateway services to use a certificate IIS must be set to all unused addresses.

Once change now it works.

Thank you,

Walter Beach

Hi Walter,

Glad that you have resolved the issue and thank you for your sharing.

Have a nice day.

Its because in your remote desktop certificates you have a certificate in there that is wrong. Hence the weird where is this certificate coming from even though everything is set correctly. If you delete that certificate it will instantly start working.

also follow this http://blogs.msdn.com/b/rds/archive/2010/04/09/configuring-remote-desktop-certificates.aspx

to setup remote desktop certificates.

the full path is MMC > certificates > remote desktop > certificates