Jump to content

kamiran.asia

Members
  • Content Count

    200
  • Joined

  • Last visited

  • Days Won

    1

kamiran.asia last won the day on January 7

kamiran.asia had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    United Arab Emirates
  • Interests
    ESET Softwares

Recent Profile Visitors

2,884 profile views
  1. ESET file Security 6.5 is currently supported for XP. Why it is become yellow and alert users to upgrade on Server 2008? While it will work on windows Xp after April 15th 2021. It seems that this alert in windows 2008 is not correct because it will not facing problem after April 15th 2021. Am i right or not ?
  2. Thank you dear , We contact Distributor, They Said there is noway to support non updated WinServer2008 ! right now ESET support winXP with ver 6.5 , Why 2008Server will not support with FS 6.5 ? What can we do right now ?
  3. Hi Dears. Many of our customers have Windows Server 2008 or 2008R2 that Sha2 Updates can not be installed. ( because of Technically problem or Rollback SHA2 updates) Version 6.5.12018.0 just became yellow this week ! While support-eol.eset.com show that FS 6.5.12018 wil not have SHA2 problem on Server 2008 (Not Updated) What can we do ?
  4. just AntiRansomeware Rulles is setup in HIPS Rules as mentioned in ESET website. No other HIPS rules . you mean if we disable Endpoint Self Defense it will solve this problem ?
  5. Hi dear ESET Admins. In some endpoint we are facing this problem : ( Upgrading 7.0.579.0 to 8.0.1238.0 ) MSI (s) (40:9C) [11:01:33:439]: Product: ESET Management Agent -- Error 1921. Service 'ESET Management Agent' (EraAgentSvc) could not be stopped. Verify that you have sufficient privileges to stop system services. Error 1921. Service 'ESET Management Agent' (EraAgentSvc) could not be stopped. Verify that you have sufficient privileges to stop system services. Full Log is Attached. What can we do remotely for this problem ( except safemode and uninstaller tool ) ?
  6. Ok , Yes we use Run Command . But it was a special problem . Thank You.
  7. Hi Dears. We have a problem in upgrading agent 7.0.579 to V8 in one of our customers network. ESET Protect V8 show Agent v7.0.579 as Updated ! So Upgrade task will finish successfully without any changes !! Repository in Online. We install a New Server and transfer Database to new server , Problem is persist. Upgrading with GPO will work ! but Upgrade Task will not work because ESET says it is up-to-date !
  8. It seems that there is a problem in ISP , We will work on this problem , Thank You Very Much.
  9. Hi Dear Marcos and thank you for your rapid response as usual 😍 the Log is attached. logs.txt
  10. Hi Dear ESET Support. We have problem in our Mail Security For Exchange. As You can see in Screen Shot of Mail Security , Anti-Spam Connection is limited. We have ping connection to all these servers : h1-ars01-v.eset.com 91.228.166.61 h1-ars02-v.eset.com 91.228.166.62 h1-ars03-v.eset.com 91.228.166.63 h1-ars04-v.eset.com 91.228.166.64 h1-ars05-v.eset.com 91.228.166.65 h3-ars01-v.eset.com 91.228.167.36 h3-ars02-v.eset.com 91.228.167.67 h3-ars03-v.eset.com 91.228.167.68 h3-ars04-v.eset.com 91.228.167.74 h3-ars05-v.eset.com
  11. As our test in our company ESET IDS can block Zerologon as this detection and block attacker IP for 1 hour :
  12. No Dear , Problem is Why IDS in 2008R2 did not block communication from attacker ip . attack will block but communication will not block for 1 hour for attacker IP. So hacker can attack over and over again. As you know when IDS block an IP address , All communications is block for 1 hour ( Ping , ... ) It seems that it is a bug or may be a lake of security in 2008 R2.
  13. Yes Dear , As you can see in the picture we have Network section and attack is detected and Attacker Ip is listed in Black list of IDS.
  14. Dear ITMan , This problem is just in 2008 R2 , In 2012 , 2016 , 2019 , ESET IDS Detect CVE-2020-1472 , and The Attacker ip Blocked ! while other Security vendors like kaspersky , bitdefender and mcaffe ( As we tested ) did not detect this attack. we use picuslabs tool for this attack test . https://github.com/picussecurity/picuslabs/tree/master/CVE-2020-1472 Zerologon Also we test Other CVE-2020-1472 scripts and the result was the same as picuslabs tools. the Question is why at 2008 R2 Attack is blocked but attacker IP not blocked even when it is listed in Blacklist IP list
×
×
  • Create New...