• Rss
  • LinkedIn
  • Youtube
  • Twitter
  • Instagram
  • English English English en
  • Deutsch Deutsch German de
Sales: +49 5251 304-800 | Support: +49 5251 304-636
NoSpamProxy
  • PRODUCT
    • NoSpamProxy Cloud
    • NoSpamProxy Protection
    • NoSpamProxy Encryption
    • NoSpamProxy Large Files
    • NoSpamProxy Disclaimer
  • RESOURCES
    • Documentation
    • Forum
    • Webcast Training
    • Training Courses
    • Support
    • Software Download
  • PARTNERS
    • Finding Resellers
    • Becoming Reseller
    • Partner Portal
  • COMPANY
    • Contact
    • Team
    • Testimonials
    • Career
    • Events
  • PRICE REQUEST
  • BLOG
  • FREE TRIAL VERSION
    • Price Request
    • Free Trial Version
  • English
    • Deutsch
  • Search
  • Menu Menu
Info Icon

Microsoft forces secure connections to Domain Controller from March onwards

All Topics, Tech & Support

In March, Microsoft will suppress insecure connection requests to Windows domain controllers. This change was announced in August. NoSpamProxy customers can sit back and relax because they only have to check the Active Directory synchronization of NoSpamProxy – in case this hasn’t already been done. If necessary, firewall ports will have to be adjusted.

What needs to be changed in NoSpamProxy?

The connections to the Active Directory are maintained under People and Identities > Domains and Users. By default, the connections to the domain controller are unencrypted. To activate encryption, the checkbox “Enable encryption (recommended)” must be set in the properties of the automatic user import on the “Active Directory Connection” tab. From now on, all connections to the domain controller will be encrypted. If a firewall exists between the server with the intranet role and the domain controller, ports may have to be adapted. Please use the following table as an orientation for which ports are used with which settings:

Server selectionUnencryptedEncrypted
Auto-discover and use a global catalog server3268 TCP3269 TCP
Auto-discover and use a standard domain controller389 TCP636 TCP
Use a specific domain controller389 TCP636 TCP

Further information on the modification

If you need more information and background on the upcoming change, please visit the Frank Carius page. On his MSXFAQ.de page you will find a comprehensive article (German only).

  • share 
  • share 
  • tweet 
  • email 
16.12.2019/by Stefan Feist

SEARCH

PRODUCT

  • All Topics
  • NoSpamProxy Cloud
  • NoSpamProxy Protection
  • NoSpamProxy Encryption
  • NospamProxy Large Files

You need support?

You can find more information about NoSpamProxy in our documentation and forum.

CATEGORY

  • All Topics
  • News
  • Product
  • Tech & Support
  • Events
Subscribeto RSS Feed

NoSpamProxy

  • NoSpamProxy Cloud
  • NoSpamProxy Encryption
  • NoSpamProxy Large Files
  • NoSpamProxy Disclaimer
  • Price request
  • Team
  • Career
  • General terms and conditions
  • Data Protection Information for Business Partners and Applicants
  • Cybersecurity (PSIRT)

Partners

  • Becoming a reseller
  • Partners
  • Order Certificates
  • Newsletter

Categories

  • All topics
  • News
  • Support
  • Updates
  • Order certificates

Latest News

  • Info Icon
    New SwissSign MPKI: What you need to do now28.09.2023 - 14:53
  • MalDoc in PDF Gefahr durch in PDFs versteckte Word Dateien Preview
    MalDoc in PDF: Danger from Word files hidden in PDFs08.09.2023 - 16:57
  • NIS2 Network and Information Systems Directive Preview
    NIS2 – What the directive means for you08.09.2023 - 09:00
IMPRINT • EULA • Privacy Policy • Change Cookie Settings • © 2023 Net at Work GmbH
  • Rss
  • LinkedIn
  • Youtube
  • Twitter
  • Instagram
New version NoSpamProxy 13.1UpdateEmotet – öffentliche Einrichtungen im Visier der Cyber-KriminellenEmotet: Public Institutions Increasingly Targeted by Cyber Criminals
Scroll to top