By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Having trouble with RDP Into Instance

0

Hi! I'm hoping someone out there can shed some light as to what's going on with my issue. I haven't been able to RDP into my Windows Server instance and I'm not sure what's wrong at this point. Any time I try to get the password for Windows Admin account, I always receive a "Password not available yet" message, no matter how long the instance has been spun up. Here's what I've verified:

  1. I have a security group with a rule that allows RDP traffic from my company's IP over the correct port (3389)
  2. The VPC assigned to my instance has "DNS Hostnames" enabled
  3. The instance has a publicly reachable DNS hostname (both one generated by AWS and a custom, registered one).

I've also tried connecting to it using the Session Manager, but my instance never shows up in the console even though an IAM role with the correct permissions is assigned to it.

A coworker of mine configured the AMI and the Instance and was able to RDP into it before, but something has changed. Said coworker has since left the company, so I am unable to ask him questions. I am also not sure what version of Windows Server was used for the AMI, as he left very little documentation and I can't seem to find that information anywhere, even on AWS.

Topics
Compute
Tags
Windows Provisioning
Language
English
FghtrOfTheNightman
asked 4 years ago240 views
3 Answers
0

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/common-messages.html

Not sure if you have read that.

I also install a separate way to access a window instance besides RDP.

I use both RDP and rviewer / teamviewer

piken2
answered 4 years ago
0

I have read that, yeah. Unless I'm misunderstanding the docs, I can't confirm whether EC2Config is enabled or not because I can't connect to the instance :/.

I haven't tried teamviewer, so I'll have to give that a shot!

FghtrOfTheNightman
answered 4 years ago
0

So I've finally tracked down the cause of my issue.

The subnet for the vpc I was using did NOT have an inbound rule allowing RDP traffic. I also didn't have an Elastic IP address associated with my instance (which I wasn't sure was necessary, since I had a publicly reachable domain name configured). Once I added both of these, I was able to initiate a connection with instance.

Now I'm trying to get Session Manager to connect, but that's a different issue I think.

FghtrOfTheNightman
answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content