Might have come across another post which got me thinking! Looks like my issue is different as the ESET itself was blocking the agent from communicating, it made initial connection then stopped! making me think it was the server, but it seems once the policy had come across, ESET then detected a change to the application and blocked the replication! Allow the communication then resolved my issue.... Adjusting my policy to exclude this from "APPLICATION MODIFICATION DETECTION"