Dan.Gurney

Nope, I only restarted it as a test. So currently unaffected systems (i.e. those which haven't been rebooted) will continue to work. Anything that got rebooted and subsequently stopped working will need the fix applying.

Not conclusive but I have just updated and restarted one of our servers which wasn't rebooted while this situation was going on. Seems to be ok. Looks like anything which is still communicating with an ERAS will be ok as long as the mirror is up to date (12303 or later)

Apparently they have a fix in testing.

Just off the phone with ESET support. Looks like this may not be an isolated issue. TBH we haven't considered an update. We have a number of update projects running through change management at the moment and up to now it AV hasn't been an issue. My understanding, admittedly based on not much reading, is that if we move to v6 we'd have to do it across the board (servers, workstations, ERAServer)?

Further info: not just RDS but all servers. After reboot = "Error opening socket"

Hi, We have ESET ERAS 5.05 serving circa 175 clients, and ESET File Security 4.5.12011 on all servers. We have about 12 virtual servers running on Hyper-V 2008 which have suddenly stopped communicating with the ERAS as of last night. When I try and manually update them from the mirror I get "Error opening socket". If I manually uninstall and reinstall File Security it works ok, until I reboot at which point it stops again. This behaviour is consistent across all the RDS servers, while none of the rest of the estate appears to be affected. I thought about it being some sort of policy change but forcing a policy update before the second reboot in the above scenario doesn't break it. I have also tried looking at netstat and there's nothing using the ports in question. I can see it communicating on 2222 before the second reboot but after the reboot; nothing. The firewall on all machines is off. Does any one have any ideas? Cheers, Dan