0

I have AWS managed MS AD standup and running. Created a jump node and joined the domain. I was able to execute ldp.exe and establish connection to one of my AD controller whose address is like (port 389): COMPUTERNAME.MYADNAME

I am trying to connect to same Domain controller from ApacheDS on my laptop, but getting error message, can't connect.

I looked at security groups attached to DC and all relevant ports are open. Any idea what am I missing?

This seems like connectivity or some firewall block issue, but couldn't find where it is.

  • Check you have an internet gateway attached to your VPC, and a route from the VPC to the internet gateway. – Tim Jun 2 at 9:12
  • @Tim Yes, all other traffic to other instances in same VPC working fine. – kosa Jun 3 at 2:03
  • What diagnostics have you done? Can you ping the instance? Can you connect to say a web server on port 80? Can you connect to it in any way? Have you tried connecting from another instance in the same VPC? Have you checked the instance firewall? You need to give us more to be able to help you. – Tim Jun 3 at 2:22
  • I have a webserver in same VPC AD deployed to. I can ping, reach out on port 80, SSH into this webserver. --> This confirms that there is no VPC level traffic block. I made sure port 389 also open in security group so that LDAP can talk on that port, but no luck to LDAP to AD. – kosa Jun 3 at 15:59
  • Then my best is it's a firewall at one end or the other. As I suggested, set up a spot instance and try to connect from that, if it works that suggests it's a firewall or problem on your client side. – Tim Jun 3 at 19:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.