Guest User!

You are not Sophos Staff.

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

sophos clients win7 no internet this AM feb 5

hey i have a few workstations today that spontaneously around 930am - 10am lost their ability to connect to the network. i also notice that the sophos endpoint icon has changed today from what it was last week. The affected terminals all seem to be win7 but i cant find any other similarities.

 

is this a known issue?

 

last update posted to the machine was 10.8.1 VE3.71.0 Update Successful



This thread was automatically locked due to age.
Parents
  • Not a fix but a current workaround we have found is to log in as a local admin user without network and disable all runtime protection services on the local machine and reboot. While making sure the server policy has been changed to also disable these settings.

  • I'm seeing similar behaviour on Windows 7 machines, Windows 10 machines fine.

    This is across 2 separate networks, both are running off SBS2011.

    Same with them updating to the latest version of Sophos with the new icon.

    Even logging on as a local user I haven't been able to access the network/internet until removing the PC from the domain.

    Once removed from the domain network/internet access is restored and works fine.

     

    Taking the machines off the domain and re-joining has resolved this for me.

    I'm hoping this doesn't occur on the main network though.

Reply
  • I'm seeing similar behaviour on Windows 7 machines, Windows 10 machines fine.

    This is across 2 separate networks, both are running off SBS2011.

    Same with them updating to the latest version of Sophos with the new icon.

    Even logging on as a local user I haven't been able to access the network/internet until removing the PC from the domain.

    Once removed from the domain network/internet access is restored and works fine.

     

    Taking the machines off the domain and re-joining has resolved this for me.

    I'm hoping this doesn't occur on the main network though.

Children
No Data