Bqtter Posted September 14, 2016 ID:1061779 Share Posted September 14, 2016 <br class="Apple-interchange-newline"><div id="inner-editor"></div> Our proxy server blocks the activation of the new beta 8 release. Which IP address, weneed to share, so that the activation can be done? Link to post Share on other sites More sharing options...
1PW Posted September 20, 2016 ID:1062819 Share Posted September 20, 2016 Hello Bqttr and Using the native Windows built-in zip utility, please create the following .zip archive file for MBARW developer team analysis: Please create a .zip archive file (not .7z or .rar) of the directory C:\ProgramData\MalwarebytesARW\. Please attach the .zip archive to your next reply. Thank you for your beta testing contribution to the Malwarebytes Anti-Ransomware (MBARW Beta) project and your valued feedback. Link to post Share on other sites More sharing options...
sllorep Posted October 12, 2016 ID:1066419 Share Posted October 12, 2016 My hardware firewall / transparent proxy blocked activation too, I allowed *.mwbsys.com through unfiltered and then closed and open MWBARW. Link to post Share on other sites More sharing options...
Allex Posted October 25, 2016 ID:1068322 Share Posted October 25, 2016 If you are trying to install Malwarebytes Anti-Ransomware on workstations of a corporate network environment, you need to release on the Firewall / Proxy (network appliance) the following IP addresses: - 174.129.216.54 - 173.194.207.139 - 52.3.94.117 - 52.20.152.22 - Ports: 80 and 443 It corrected the application activation problem and starts Real-Time Protection normally. NOTE: Also check that the Windows Firewall is configured to release the following executables: - MB3Service.exe (Malwarebytes AntiRansomware Service) - mbarw.exe (Malwarebytes AntiRansomware Application) Link to post Share on other sites More sharing options...
Root Admin AdvancedSetup Posted October 26, 2016 Root Admin ID:1068534 Share Posted October 26, 2016 Hello @Allex and Thank you for your input but using IP instead of name resolution and using port 80 is not a preferred method. That will prevent automatic round-robin scripts from locating the best and fastest server to serve up updates. Please refer to: https://www.malwarebytes.com/pdf/guides/AntiRansomwareAdminGuide.pdf - Page 2 - External Access Requirements. Thank you. Ron Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now