RD Connection to Server 2003 R2 broken after installing RD Gateway on Server 2008 R2

I installed RD Gateway on my RDS server (2008 R2), which installed Network Policy Server as well. After installing, I could no longer connect via Remote Desktop from any machine on the network to one particular server running Server 2003 R2. I get this error:

"The remote computer requires that authentication be enabled to connect. The connection cannot proceed because authentication is not enabled."

Nothing was changed on the 2003 machine, and it doesn't have these options. I've removed the RD Gateway and Network Policy Server, but the problem remains. No other machines are affected. Again, I changed nothing on the 2003 server, and I've been connecting to it just fine for years, right up until I installed RD Gateway.

Any clues?

Thanks, Ron
ronleepdxAsked:
Who is Participating?
 
Randy DownsOWNERCommented:
Maybe this will help.

Seemingly the cause of the failure is the lack of certificate under the RDP-Tcp properties screen.  Security Layer is set to SSL, Encryption Level is set to High but the Certificate field is blank.  No matter what I do it doesn't want to automatically put a certificate in there, whereas there is one  for 2008.

I have managed to get a certificate on there by manually requesting a certificate from the 2003 server, deleting the existing RDP-Tcp connection and re-creating it
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.