Comments on: AWS: AD Connector – Use on-prem AD credentials to log to AWS https://blog.andreev.it/2017/09/113-aws-ad-connector-use-prem-ad-credentials-log-aws/ Sat, 24 Oct 2020 13:31:54 +0000 hourly 1 By: Kliment Andreev https://blog.andreev.it/2017/09/113-aws-ad-connector-use-prem-ad-credentials-log-aws/#comment-217 Sun, 11 Nov 2018 12:14:15 +0000 http://blog.iandreev.com/?p=3209#comment-217 In reply to J Lumford.

Mine DCs are 192.168.1.4 and 5 but they are at home, not in AWS. Are you saying that your DCs are in AWS?
I also have a VPN between AWS and home so I can use the internal AWS IPs to reach them.
Also, check if the reverse DNS works for your DCs.

]]> By: J Lumford https://blog.andreev.it/2017/09/113-aws-ad-connector-use-prem-ad-credentials-log-aws/#comment-216 Sun, 11 Nov 2018 02:19:28 +0000 http://blog.iandreev.com/?p=3209#comment-216 Hi – Thanks for the above info. I have been trying for DAYS to create an AD connector pointing to an AD that I stood up on AWS EC2, but am still failing. The error I usually get is that it cannot find the DNS server (connectivity error), but I have run the directory test tool and that is fine.

I think I have a theory what might be going wrong. In the page where you enter the details, you enter the IPs of the two ADs, right? In your example above, you had 192.168.1.4 and 192.168.1.5, right?

I do that also (enter the IP of my AD machines).

However, when I submit the form, then it changes from “Requested” to “Creating” and I look at the info in the page, the IPs are not the ones that I entered for the IPs of the DNS server. Instead, the IPs appear to be completely RANDOM!!

I don’t know WHY they are random, but they are definitely NOT what I entered.

Do you (or does anyone else) have any idea why those IPs would be different from the IPs that I entered?

Thanks,
Jim

]]>