Messaging Gateway

What's New

  • Join our customer advocacy platform!

    You are invited to join Symantec Gold, our online customer advocacy platform. When you sign up, you’ll be able to participate in daily challenges where you provide product feedback, receive notifications about upcoming webinars, and so much more! Every challenge you do, you’ll earn points that you can redeem for some Symantec SWAG.

  • Catalyst 2020 Content On Demand!

    Did you miss Catalyst 2020 or did you attend and want to catch a session that was happening at the same time as one you attended?

    Catch all of the Catalyst 2020 sessions on demand until Oct 29. Hear how Symantec is reinventing what it means to be a leader in cyber security as we invest in the industry’s broadest and deepest set of threat intelligence capabilities. Listen to high-profile experts sharing their perspective on the constantly evolving threat landscape, and the latest thinking on cyber security in a post-pandemic world. 

    If you attended, head directly to the Catalyst 2020 site and log in using the same credentials they used on the day.

Latest Discussions

  • @tpa thanks for your reply. This might be the problem as if I try only LDAP with 389 and use the same BIND DN as I use with LDAPs I get the incorrect username and password if I try with LDAPs port 636 with the same BIND DN I get ​​​ "Unable to search ...

  • @Steven R thanks for your reply. I really appreciate it. Did you check the screenshots? do they make any sense to you? Also from the CC I can telnet fine to the DC on port 636 and 389. When I use the fqdn of DC and use port 636 with the bind DN in ...

Most Active Users