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

Protected computers still showing as greyed out in Enterprise console

SN

Hi

I'm having a problem where by computers i have protected through the enterprise console are not showing as protected even though the sophos client installed correctly and updates without problems.

Basically the same computers were protected and showed fine when installed with win XP.  I have recently upgraded all the desktops to Win 7 and protected them from console but they do not show as protected. 

On some of the computers i had to manually run the sophos install from task scheduler.  The machines have the same SID from when they had XP installed and Sophos is gathering information from AD.  Server is domain controller running win 2k8 R2 SP 1 and enterprise console 4.5.

I would really appreciate some help on this.   Thanks

:12209


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

    I wanted to add to this thread because I had the same symptoms, but the fix was slightly different.

    We have always opened the ports in the firewall of 2008 servers by using the following batch file:

    netsh firewall add portopening TCP 8192 "Sophos Management"
netsh firewall add portopening TCP 8193 "Sophos Management"
netsh firewall add portopening TCP 8194 "Sophos Management"
netsh firewall add portopening TCP 8081 "Sophos quarantine digest"

    I recently did a migration from a SBS2003 to SBS2011.  When I ran the above commands on the SBS2011, it mentioned that the 'netsh firewall' command has been deprecated and to use the 'netsh advfirewall firewall' command instead.  However, it said the commands completed successfully, so I didn't give it much thought.  Everything looked fine in the Sophos console.

    A couple days go by and I check back on the Server, and all clients are shown as disconnected.  D'oh! 

    Long story short, after much troubleshooting including the steps in this thread, I took another look at the batch file we used to open the firewall.  Here is the correct batch file for the newer firewall commands:

    netsh advfirewall firewall add rule name="Sophos Management 1" dir=in action=allow protocol=TCP localport=8192
netsh advfirewall firewall add rule name="Sophos Management 2" dir=in action=allow protocol=TCP localport=8193
netsh advfirewall firewall add rule name="Sophos Management 3" dir=in action=allow protocol=TCP localport=8194
netsh advfirewall firewall add rule name="Sophos Quarantine Digest" dir=in action=allow protocol=TCP localport=8081

    I deleted the existing Sophos records in the firewall, and ran the newer batch file.  The console came to life almost immediately.

    Hope this helps someone else down the road!

    :14311
Reply
  • 0

    I wanted to add to this thread because I had the same symptoms, but the fix was slightly different.

    We have always opened the ports in the firewall of 2008 servers by using the following batch file:

    netsh firewall add portopening TCP 8192 "Sophos Management"
netsh firewall add portopening TCP 8193 "Sophos Management"
netsh firewall add portopening TCP 8194 "Sophos Management"
netsh firewall add portopening TCP 8081 "Sophos quarantine digest"

    I recently did a migration from a SBS2003 to SBS2011.  When I ran the above commands on the SBS2011, it mentioned that the 'netsh firewall' command has been deprecated and to use the 'netsh advfirewall firewall' command instead.  However, it said the commands completed successfully, so I didn't give it much thought.  Everything looked fine in the Sophos console.

    A couple days go by and I check back on the Server, and all clients are shown as disconnected.  D'oh! 

    Long story short, after much troubleshooting including the steps in this thread, I took another look at the batch file we used to open the firewall.  Here is the correct batch file for the newer firewall commands:

    netsh advfirewall firewall add rule name="Sophos Management 1" dir=in action=allow protocol=TCP localport=8192
netsh advfirewall firewall add rule name="Sophos Management 2" dir=in action=allow protocol=TCP localport=8193
netsh advfirewall firewall add rule name="Sophos Management 3" dir=in action=allow protocol=TCP localport=8194
netsh advfirewall firewall add rule name="Sophos Quarantine Digest" dir=in action=allow protocol=TCP localport=8081

    I deleted the existing Sophos records in the firewall, and ran the newer batch file.  The console came to life almost immediately.

    Hope this helps someone else down the road!

    :14311
Children
No Data