389 vs. 636

federale
New Contributor

Hello out there - having issues with out-of-the-box Microsoft AD binding in OS X.15.6 that even with command line packetencrypt forced, I still see lots of port 389 traffic when I believe it should be 636.

I am not wise enough to understand what is going on. What do I need to know/do?

0 REPLIES 0