jduvillard
-
Posts
9 -
Joined
-
Last visited
Posts posted by jduvillard
-
-
Yes indeed!
I was missing a Rogue Sensor policy which allowed me to blacklist the IP addresses of our printers and non-computer devices.
This may not solve the original problem, but things are looking a lot more tidy now.
Thank you Ben
-
It sounds like I am the only person affected by these issues.
Am I missing a trick here?
-
Hello,
ERA Version 6.1.444.0 installed on Windows Server 2008 R2 SP1
I have 2 issues with the rogue detection service:
1- As far as I can see, some computers in the list of rogue computers don't exist in any DHCP, DNS or AD tables. Where is the rogue information coming from?
2- I have many printers and routers in this list with the wrong name associated with the MAC addresses. When I move them to a Static Folder, they are removed from the rogue entry list (which is good), however as soon as I rename them in my static folder, they appear again in the rogue list.
Any suggestion?
JP
-
I had at least 2 remote computers crashing every night for a month.
Since I have installed KB2664888 on all our remote desktops 2 weeks ago, I have not had a single crash.
Thank you for sharing LocknetSSmith
-
Quick update. Nothing has so far worked apart from disabling File Open.
So I will wait for EFSW 6.2 to be released.
-
Thank you Marcos and Mitsol for the replies.
Our backup is done on tape so I have now disabled the option "Real Time FS protection>Media to Scan>Removable media". I will keep you posted, whether this works or not.
JP
-
Update, in case someone has some new ideas:
So far I have corrected the exclusions, which were incorrect: from C:\Program Files\Symantec\Backup Exec\ to C:\Program Files\Symantec\Backup Exec\*.*
This didn't make any difference
I have also tried: C:\Program Files\Symantec\Backup Exec\*
Same result
I have added all the Backup exe programs manually: C:\Program Files\Symantec\Backup Exec\beremote.exe , C:\Program Files\Symantec\Backup Exec\beserver.exe , etc...
This didn't make any difference either
The only thing that still makes a difference is by disabling the Scan on File Open
Any thoughts?
-
Hello,
This is a follow up on this thread: https://forum.eset.com/topic/753-eset-file-security-backup-processes/
Our backup is slowed down to a point where people start arriving in the office before the backup is finished.
The only solution I have found to work is by setting: Real-time file system protection > Scan On > File Open to disabled
I would rather have exclusions in place, but excluding the Symantec programs path:
E:\Program Files\Symantec\Backup Exec\
didn't work
Has anyone found a solution for this?
Many thanks
Jean-Philippe
P.S.: Our system is running ERA Agent 6.1.444.0 and File Security 6.0.12035.0 on Windows Server SBS 2008 SP2
Remove non-computers from Rogues list
in ESET PROTECT On-prem (Remote Management)
Posted
https://forum.eset.com/topic/5323-rogue-entries-in-era6/?hl=rogue
I had the same problem, you can create a policy that only applies to the rogue sensor. In this policy you can then blacklist some known IP addresses under the IPv4 filter.