Hello Jayshree -
When you mention non-secure & secure ports, are you referring to ports 389 and 636? If so, I've experienced similar issues in AWS Linux 2. When using port 389, you will likely pick up the local domain. Once you refer to port 636, you might need to refer to a different domain when you configure the identity store in Tableau Server. I suggest you speak with the AD administrator for some guidance. Hope this helps.
Thank you so much for your response.
I checked with my team, they have confirmed the below issue, but the solution mentioned is not helping out them!
do you know anything about this?
Hi Jayshree, did you raise a ticket with Tableau Support about this?
Have run into this issue installing 2019.2. Are you configuring SSL when you set ldaps and port 636? If you follow the ldap/ssl setup steps that solved the issue for our installation.