Jump to content

Ashkaan

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by Ashkaan

  1. 16 minutes ago, Marcos said:

    Theoretically creating an application-agnostic rule should work.

    Ya, but I don't think anyone has done the work to figure out what ports Teams uses.  Also, it might be that malware traverses those ports too.  Or, Microsoft adds a port without telling anyone.

    I have a ticket with Microsoft and they are refusing tell me what ports and protocols their app uses.

  2. 5 hours ago, conorc said:

     

    They added a new app pathway in the latest update and it also needs allowed on the firewall, it is (Renderer)

    
    /Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper (Renderer).app/Contents/MacOS/Microsoft Teams Helper (Renderer)

     

    Thank you so much!  I'll try this immediately and report back!

  3. On 9/28/2020 at 9:04 AM, PuterCare said:

    I just had a reply from Eset tech support and they suggested adding rules for the following, I already had the first two so hopefully the third rule will be what resolves for me. I don't have the systems available to me right now to test.

    /Applications/Microsoft Teams.app
    /Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper.app
    /Applications/Microsoft Teams.app/Contents/Frameworks/Microsoft Teams Helper.app/Contents/MacOS/Microsoft Teams Helper
     

    This does not work.  Users are still have constant dropped Teams calls.  With the Firewall completely off, it's perfect.

×
×
  • Create New...