- Newest
- Most votes
- Most comments
You could RDP from an Android device previously but not today, from the same device? Verify everything is exactly the same as it was before on the client and server side. Check in the AWS console that your instance is still running. Verify its Security Group has an ingress rule allowing RDP, that its subnet has open ACLs and a default route for 0.0.0.0/0 to the Internet Gateway.
You could try briefly running another small instance to help debug, it will cost very little.
What's the inbound rule of your security group ? Ensure the port 3389 is open in that rule and the specified IP range or IP address matches the source of the connection.
When you setup the security group, did you select access from anywhere (0.0.0.0/0) or only for your IP? if it's the latter then that will allow access from whatever your IP was on that device at the time the security group was created, which may be different to today (you will get a different IP on cellular as opposed to home or office wifi, and also your home wifi's IP may change periodically depending on your ISP).
Check the current IP of your device on whatismyip.com and verify that address is allowed ingress on port 3389.
Relevant content
- Accepted Answerasked 6 months ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
I have a similar error and on free tier AWS instance also that started a month ago. I'm not sure if this post was resolved. Back then, it was working fine. I temporarily disabled the windows firewall as an app installation is getting a proxy server error. I got disconnected and unable to connect since then and getting this error.
Make sure that the remote computer is turned on and connected to the network and that remote access is enabled.
Error code: 0x204 Extended error code: 0x0