Forum Discussion
Azure ATP sensor : Could not create SSL/TLS secure channel
Hi All, I have multiple DC on which Azure ATP sensor is working fine, however on one of Domain controller 2008 R2 server it is throwing below error Error ExceptionHandler Microsoft.Tri.Infras...
EliOfek
Microsoft
MicrosoftCan you elaborate on the npcap install?
was npcap 1.1 pre installed for a different reason before you deployed the sensor ?
If so, was it deployed with the correct parameters ? (compatibility, no admin only)
And which parameters were used when you deployed 1.0 ?
was npcap 1.1 pre installed for a different reason before you deployed the sensor ?
If so, was it deployed with the correct parameters ? (compatibility, no admin only)
And which parameters were used when you deployed 1.0 ?
There was some testing of issues at some point prior to ATP sensor install, with wireshark. It was in place from their installer. We have 6 DCs running atm at that location and this was the only 1 with issues. The others are all using npcap 1.0. The process was the standard microsoft (https://docs.microsoft.com/en-us/defender-for-identity/technical-faq#winpcap-and-npcap-drivers) one, with npcap 1.0 from the downloaded folder. NPCAP is up to v1.70 now. I assume that upgrading to the current version is beneficial?
- EliOfekWe don't lock down to a specific npcap version, so in theory you can upgrade to 1.70 and it might just work.
If you run into issues with 1.70 you can open a support case with us, and we will try to work with Npcap to resolve this in best effort mode.
The main problem is that we didn't test 1.70 with MDI so we can't say it will work well without any issues. 1.0 was tested heavily in the past.
We did not test newer versions as 1.0 is very stable (we worked hard for a few months with npcap to make sure it is), and there are no known CVE's or issues that will interrupt MDI with it.