Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 10284 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC 5.5.1 open Ports for Policy

Joa See

Hello,

I run the SEC 5.5.1 on Windows Server 2016 with web server. Because of the many laptops. The primary update source is the web server, second update source is unc share.

I have the bad feeling that not all policies are transferred correctly (for example: if the on-access scan is disabled, I can not activate it by policy)

The following ports I have enabled in the firewall: TCP: 80, 137, 138, 139, 389, 443, 445, 636, 2195, 3268, 5432, 5433, 8081, 8190, 8191, 8192, 8193, 8194, 18080, 51234.

Have I forgotten a port?

 

Thanks for any Information.

Joachim



This thread was automatically locked due to age.
Parents
  • 0

    Hi  

    I don't think other than above-mentioned ports are needed to make it work. Apart from this, I'd request you to check the communication between client and server in both directions because we have seen such scenarios where the configuration is proper on server and firewall side but sometimes, needed ports are not open on client-side. Please refer to this article for needed ports on all the nodes.

Reply
  • 0

    Hi  

    I don't think other than above-mentioned ports are needed to make it work. Apart from this, I'd request you to check the communication between client and server in both directions because we have seen such scenarios where the configuration is proper on server and firewall side but sometimes, needed ports are not open on client-side. Please refer to this article for needed ports on all the nodes.

Children
No Data