text: The Connection Cannot Be Completed Because The Remote Computer That Was Reached Is Not The One You Specified
  Posted on November 9, 2012 by Webmaster	3 Comments
  When connecting via RDP (Remote Desktop Services / Terminal Server), you may get the following error:
  This can be caused by the following things:
  The time being incorrect on the Terminal Server
  You may need to run ipconfig /flushdns on the client and Terminal Server
  You may be connecting to a Terminal Server by typing it's name when the Terminal Server is part of a farm. In this case you can get The connection cannot be completed… because your RDP client has been redirected to another server in the farm, so the server name you typed into your RDP client does not match the certificate for the Terminal Server you have been redirected to. To fix this run the RDP client in console / admin mode (type mstsc /admin in the command prompt to open the client in admin mode or mstsc /console in Windows XP or older operating systems)
  The Connection Cannot Be Completed Because The Remote Computer That Was Reached Is Not The One You Specified, 9.3 out of 10 based on 6 ratings
  Tags: RDP, Remote Desktop Services, Terminal Server
  3 thoughts on "The Connection Cannot Be Completed Because The Remote Computer That Was Reached Is Not The One You Specified"
  Jason on February 12, 2013 at 11:33 am said:
  I had a thin client that, after working fine for over a year, decided it would not connect to the Remote Desktop Server any more with the above error.
  Turns out the time zone on the Thin Client had reset to somwhere else and the clock was wrong.
  Reset the time zone and the clock and all worked again. 🙂
  Lewis on February 12, 2013 at 1:59 pm said:
  Funny, usually you get an authentication error when the time is wrong on the computer… I've never had the remote computer that was reached is not the one you specified from the time being wrong 😕
  Thanks for sharing that one! Hopefully that will help somebody.
  IT Warrior on February 15, 2013 at 8:22 am said:
  It happened to me and it turned out the server time was wrong. had to fix it.. what a weird problem.