Jump to content

AshleyTaylor

Members
  • Content Count

    7
  • Joined

  • Last visited

Contact Methods

  • Website URL
    http://www.csscomputers.co.uk

Profile Information

  • Gender
    Male
  • Location
    U.K.
  1. I think i have just solved this. Seems that you can add a firewall rule to allow all connections from trusted zones to trusted zones and allow all the traffic. This has fixed some other strage issues that they were having as well, so is it that Trusted Zones is just a group and not getting checked anywhere in the process.
  2. What do you mean by the Eset Authentication Server? Can you give an example, is this setable in the policys?
  3. Sorry, they are both wired and wifi. Mainly seeing it in Wired connections at the moment.
  4. Hi Guys, I am having some issues at the moment with some of my clients with ports and applications being blocked even though their subnets are within the trusted zones. Trusted zones are as follows: 10.0.0.0/255.0.0.0 172.16.0.0/255.255.0.0 192.168.0.0/255.255.0.0 ::1 FE80::/64 Even though these are trusted I still seem to need to put exceptions in the firewalls when I shouldn't need to. Any help will be appreciated.
  5. The sooner this update comes out the better as I have one huge policy for all my exceptions for my clients and this will solve this issue that I currently have.
  6. Hi Guys, I have recently noticed that Antivirus exception lists do not merge together with other policies, is this intended or a bug? I personally would like the feature to be able to have multiple policies for individual programs as we resell Eset and have one central Administrations Console. For example, if I have two policies, Policy A and Policy B. I add some antivirus exception paths to both Policy A and B and set the flag on the policies to Apply and not Force. I set B to apply last. What I would like to see is the Antivirus exceptions from policy A and B to be merged and hav
  7. Hi Guys, I have an issue at the moment with the way my policies are handles. We resell Eset using the MSP platform and have a central Eset Administration Console. We point all of our clients to this console so there is only one point of configuration. An issue has come up after I was looking at one of our clients Eset client and noticed that our AV exceptions are not getting merged together. I currently have it set up so we have a policy for each application that has exceptions. These are all set to Apply and not Force but when looking in the exception list on the Client I noticed
×
×
  • Create New...