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

Endpoint10 hangs windows 2000

Hi,

We have recently upgraded Sophos Endpoint to version 10. After few hours, Windows 2000 servers are being hanged/unresponsive. They are responding only after a hard reboot....

We did not see any issues after uninstalling Sophos. Is this a bug in Endpoint 10?

Regards,

Ranjith

This thread was automatically locked due to age.

Parents

0 Christrati over 13 years ago

We faced a similar issue with a legacy server, which will be replaced. Most of our Windows 2000 servers are running as virtual machines on Windows 2008 R2 SP1 servers, under Hyper-V. About 2 months ago, mid May, we began having network issues with a single Windows 2000 server not responding to network requests and receiving NetLogon errors. The only resolution was to force the VM off and start the VM back up, ie, a hard reboot. When compared to the other Windows 2000 server still running, the only difference was the backup agent and Sophos ver 10 (the other were running 9.5 or 9.7). I removed the backup agent, and the issue still remained. Since this isn't a critical server, we simply did a hard reboot when it was required.
At the end of June, we updated all of our Windows 2000 server to Sophos v10.0.5, as we received a notificatoni that all 9.5 and 9.7 versions would be updated the 2nd week of July. We had two additional Windows 2000 server that exhibited the exact same behavior. After a hard restart, so far, the issue hasn't reoccurred. We have 2 additional Windows 2000 servers that have not exhibited the issue, and the only difference was that they have NetBIOS enabled and pointing as a legacy WINS server. I changed the networking so they all match, ie NetBIOS enabled and WINS enabled. So far, no further lockups for almost a week.
In regards to the above post, here are our current settings on the Windows 2000 servers:
on-access - Enabled, with exclusions
on-write = off
on-rename = off
scan inside archive files is not enabled
behaviour monitoring = off
Web Protection = Off
Live Protection = Off
Chris
:26733
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Christrati over 13 years ago

We faced a similar issue with a legacy server, which will be replaced. Most of our Windows 2000 servers are running as virtual machines on Windows 2008 R2 SP1 servers, under Hyper-V. About 2 months ago, mid May, we began having network issues with a single Windows 2000 server not responding to network requests and receiving NetLogon errors. The only resolution was to force the VM off and start the VM back up, ie, a hard reboot. When compared to the other Windows 2000 server still running, the only difference was the backup agent and Sophos ver 10 (the other were running 9.5 or 9.7). I removed the backup agent, and the issue still remained. Since this isn't a critical server, we simply did a hard reboot when it was required.
At the end of June, we updated all of our Windows 2000 server to Sophos v10.0.5, as we received a notificatoni that all 9.5 and 9.7 versions would be updated the 2nd week of July. We had two additional Windows 2000 server that exhibited the exact same behavior. After a hard restart, so far, the issue hasn't reoccurred. We have 2 additional Windows 2000 servers that have not exhibited the issue, and the only difference was that they have NetBIOS enabled and pointing as a legacy WINS server. I changed the networking so they all match, ie NetBIOS enabled and WINS enabled. So far, no further lockups for almost a week.
In regards to the above post, here are our current settings on the Windows 2000 servers:
on-access - Enabled, with exclusions
on-write = off
on-rename = off
scan inside archive files is not enabled
behaviour monitoring = off
Web Protection = Off
Live Protection = Off
Chris
:26733
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data