Jump to content


  • Posts

  • Joined

  • Last visited

About haco

  • Rank

Profile Information

  • Location
  1. Just confirmed the above. I made a policy with only one firewall rule added. Setting this renders the client unable to add any firewall rule at all. Is this by design or a bug?
  2. Thanks for the insightfull answers. So If I understand correctly, as soon as I deploy a policy with some firewall rules in to a client, that client is NOT able to add ANY firewall rule anymore?
  3. Thank you for your reply. The only applied policy is the policy that was imported from ERA5. Is there a setting to lock applied settings or so in this new version?
  4. Hello, I have deployed era 6 on a new server by import from era5. Now I have the strange behaviour that a lot of the settings on the clients seem te bo locked (see attachment). That makes it impossible to add f.e. firewall rules on some clients locally. Is there somebody who can help me out on this? I'm having difficulties finding my way around the new era.
  5. So, from my tests with it, I get this. If you create zones with authentication on it, and you add those as parameters to your policies, it doesn't work. If you add the subnet of that zone to your policy, it works. Or you can add those subnets to your trusted zone as an alternative. Am I right or missing something here?
  6. I have no Idea what happened, but restored my policies by exporting them from the clients and importing it back into era
  7. Thanks for the help, for the ping, I see the rule that gets hit is apply icmp filter, but can't find that rule in my rules list. for the other things (netdom renamecomputer for example) I unchecked the necessary default rules, so they don't get hit anymore(block netbios name service requests, blok incoming netbios requests), but it still doesn't work, so I guess that there is still something else. I have created a rule that specifically allows thes ports on trusted zone and the zone I created for my remote site, and still no luck. Maybe these zones are not interpreted correctly?
  8. I installed the new version whilst the old was still present.
  9. Hello, I just updated my remote admin server and console and when logging in again I discoverd that the set password is gone, as well as my policies. I still see all clients in the list, as well as my recent connections (I used to have multiple eset remote admin servers). Is anyone familiar with this behaviour or knows where I could retrieve the old policy?
  10. Hello, long time eset enpoint user and first time forum poster here. In the RAC policy editor, we have added all our company networks as zones (and checked the mark to add them to the trusted zone). The main goal for this is to make sure the client does not have to add their company network to the trusted zone each time (via the allow sharing dialog). This works perfectly so far. The second goal is to allow some services to work between our networks without hassle. (They are all connected with company-wide vpn) More specifically, I would like to be able to ping to my clients on other sites. This does not work unless I temporary disable the eset firewall. In the firewall rules, the standard rule "Allow icmp communication in the trusted zone" is present. So, this should work right, considering that all my company networks are added to the zones, and they in their turn are checked to be in the trusted zone? To get around this problem, I tried to add a new rule to allow icmp traffic in the zones I created myself, but I am only able to select "Trusted zone","Addresses excluded from IDS", "Addresses notified about unavailability of TCP/UDP ports", "Addresses excluded from protocol filtering", "DNS servers" and "Local Addresses" as zone selection at the remote side. Any help to as what I am doing wrong?
  • Create New...