title: Timeout When Trying to Connect to AWS EC2 Windows 2012 Server with RDP/RDC with Windows 8.1 (VM)
body: <p>I have a Windows Server 2012 instance on Amazon EC2. </p>
  
  <p>Although I have been able to connect to the server with RDP (yes I HAVE connected) the connection was temperamental. Meaning, I would be working away when the screen would freeze and stop responding, then after a few minutes, it would give the "Reconnecting attempt 1 of 20..." screen and come right back - at least for a little while. </p>
  
  <p>Other times, it would not connect at all. It would allow me provide my credentials and would display a message about "Estimating connection quality..." and then a few minutes later it would give me a message saying that a "licensing error occurred..." </p>
  
  <p>The thing is, if licensing was an issue, how could I have connected before? And after rebooting my VM, how is it that I could connect again (even if the connection dropped randomly). </p>
  
  <p>I then tried from another computer (a Windows 7 laptop) and could connect, but with the same timeout problem after being in the middle of working on the server. </p>
  
  <p>To further cloud things, I was able to connect with no issues from my Windows 7 VM on my old  Mac. No timeouts, connection is fine etc. The three computers are right next to each other (old 2011 MacBook Pro with Win7 VM, new 2013 MacBook Pro with Win8.1, and Dell Laptop runnning Win7), wirelessly connected to the same router on the same network, with the same external IP. </p>
  
  <p>Even stranger, a simple website I setup on the server has trouble loading. The HTML comes over but images get hung up. </p>
  
  <p>The IT company that setup this virtual server to restrict access to our company IP only. I don't seem to see these issues externally - the loading of the website that is. </p>
  
  <p>Has anyone ever had a problem like this with EC2 or just Windows Server 2012 in general?</p>