Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 7624 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

Windows Firewall rules for Sophos console server

sjc85

Hi There,

Our organisation has just completed a migration from a Server 2008 domain platform to a Server 2012 platform.

All our host and guest servers are now running Server 2012.

I have used the relevant knowledgebase articles in order to configure a group policy for all Sophos client servers' Windows firewall rules.  These are working perfectly and are allowing me to install, configure and auto-udate all of my clients.

However, when the same GP is applied to the server which is hosting the Sophos Enterprise console, all of a sudden the clients are appearing as disconnected in the console and i'm receiving installation errors for any new installtions from the console.  Nevertheless, the installations do complete successfully, it's just that they cannot report back to the console in order to tell it.

I've removed th GP and turned off the Windows firewall again on the Sophos console server.

Can you please tell me what Rules I will need to configure in order to get this server working properly with the firewall enabled?

Many Thanks,

Scott

:37147


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

    Thanks Christian, this has resolved my issue.

    I had already included a Sophos RMS rule to allow any domain connections through port 8194 both inbound and outbound.

    However I have just added inbound and outbound rules in order to allow any domain connection through port 8192, and this seems to have solved the problem.

    Cheers, Scott

    :37151
Reply
  • 0

    Thanks Christian, this has resolved my issue.

    I had already included a Sophos RMS rule to allow any domain connections through port 8194 both inbound and outbound.

    However I have just added inbound and outbound rules in order to allow any domain connection through port 8192, and this seems to have solved the problem.

    Cheers, Scott

    :37151
Children
No Data