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

V10 Upgrade Fails

V10 auto upgraded on Thursday morning and we have machines where the upgrade has failed dismally.

All machines are Windows 7 32 bit and managed through console manager, the issues are

IE has no web access

Machines can get to file share of Sophos

Machines cant surf the web or report into the console

Services that are installed and have issues

  • Sophos Agent – stopped – if you restart, it appears to be running and then crashes after a few seconds, windows logs says crashed multiple time event ID 7031
  • Sophos Client Firewall – stopped – if you restart crashes out with no mention in windows logs
  • Sophos Message Router – stopped – if you restart crashes out with error message 1067
  • In comparing with other machines there are services missing

When you go into dos to check basic network settings we see

  • DHCP settings are correct
  • Successfully renew / release DHCP leases
  • Ping internal and external IP addresses
  • Can’’’’t ping internal or external DNS / domain names

Sophos Server can ping and can open file shares on troubled computers

We have tried removing Sophos completely ...... with no success

Tried reinstalling ...... with no success

Tried uninstalling and go back to V9.7 ...... with no success

Created new subscription group for v9.7 only and moving machines in there ...... with no success

Anyone have any ideas?

:27487


This thread was automatically locked due to age.
Parents
  • HI,

    I wonder if Winsock has problems?

    netsh winsock show catalog > winsock.txt

    might be worth a look to see what's registered.

    Maybe on one client re-set winsock and see if that helps.

    netsh winsock reset

    At least you'd know it was in the right area.

    Regards,

    Jak

    :27491
Reply
  • HI,

    I wonder if Winsock has problems?

    netsh winsock show catalog > winsock.txt

    might be worth a look to see what's registered.

    Maybe on one client re-set winsock and see if that helps.

    netsh winsock reset

    At least you'd know it was in the right area.

    Regards,

    Jak

    :27491
Children
No Data