Jump to content

kaka81

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by kaka81

  1. Again it's me: I've uninstalled Eset on 2 clients and it worked well. So it seems to be a problem with Eset resp. with the efpw lightweight filter which is installed with Eset on NICs. Any suggestions?
  2. I've got this problem right now on my own PC. nslookup doesn't work, then I've disabled Epfw LigthWeight filter on LAN adapter and IPv6, pressed OK and nslookup was working immediately. So it seems to be a problem with Epfw? If yes, how to fix this problem? Without these option no Eset firewall is working?
  3. Ok but firewall was/is disabled at all. Shouldn't it be the same? My it partner asked me if I have installed nac server at installation of eset but what I've found on the internet is nac only a plugin for Cisco devices and I haven't any Cisco device. Or does he mean something different?
  4. I've installed v6. Enabling/disabling the firewall makes no difference. What's Epfw LightWeight filter? Edit: ok, just find the option in network adapter properties. What does this option/feature exactly do?
  5. Hi, I've installed Eset Endpoint Security to our clients and since this installation my clients (~70) lose their DNS for sometime. what does that mean? - nslookup ends in an timeout -> DNS server unknown - ping to ip and domain name work well for a while - clients aren't able to print because \\dc\printer can't be found and is displayed as "offline" - sometimes an "ipconfig /release and renew" works, sometimes not, sometimes disabling and enabling NIC on clients works sometimes not, a reboot of client works sometimes and sometimes not,... - after a while (30mins, 3h, 1.5h, 10mins -> randomly) suddenly it works again. I've following configuration: - DC (Server 2012 R2 -> DNS, DHCP Server, DC, etc.) - DC02 -> Failover Server for DC, but it's not working correctly - via DHCP DNS and WINS 192.168.0.1 (dc) and 192.168.0.15 (dc02) are correctly configured - Eventviewer on server and clients doesn't give a hint what's going wrong Are there any known issues according to this problem or does someone have any idea? Thank you very much. Cheers, Christoph
  6. Hello, a few days ago I installed ERA and rolled out Eset Endpoint Security to my clients (~70). Now I got on every client permanent warning: 1) ARP Cache Poisoning Attack, Source 192.168.0.1 (this is our PDC), Target *IP-Adress of Client*, Protocol ARP 2) Identical IP-Adress located in network -> this can't be true because we use an DHCP-Server and every IP address is uses only once in our network Any idea how I can fix this issue(s)? Thank you. Cheers, Christoph
×
×
  • Create New...