Piper

Guys, Thanks for everything. It's weird however, a simple solution and hope can help other license holders as well. Maybe we've got strict carrier after all and best solution we've done was to point the DNS to Google and solved the issue. Case closed. Piper

I just hope that posting 50 topics or questions is worth, can help all MB users who bought personal and business licenses and my "personal opinion" only, sensibly not a huge factor in editing a profile. Anyways, that's the rule. Maybe there is a good reason why

Dear BRAM, Thanks for you reply, forgot to mention. Will double check on above too. Just reading the manual and on page 2, where did you get the other 3 URLs? I can only see these: https://data.service.malwarebytes.org Port 443 outbound https://data-cdn.mbamupdates.com Port 443 outbound https://keystone.mwbsys.com Port 443 outbound Thank, Piper

Dear BRAM, We did the installation outside the secure network perimeter and as mentioned unmanaged, so firewall is not causing the issue and thing for sure is that we've checked that he can access the Internet without restrictions and freely, why there is no reason that he cannot access mentioned URLs. Also as mentioned, we did the same with the IT computers who loves to work without network boundaries, so diving deep into logs is the next thing to do. However, since we have a jet setter, it's very hard to get in touch or have his unit checked for long a time. Again, it's kinda weird and for whatever reason, is the thing we need to escalate.

Dear Dyllon and Malwarebytes Staff, We've started to deploy the new version of the endpoint security to our client computers and little bit disappointed that ARW is not included in the managed solution. However, it's better having than nothing, so we deployed it across and believe to be in the 50% till late. It's unfortunate that one of the Managers in the Top Management is having the activation issues. He has Windows 7/64 and having the same as the rest of the IT personnel with unmanaged product installation. We all have successful install except for him and very unfortunate, as we've just started deploying to top management this afternoon. Any idea why it's having the attached error? Sincerely looking forward to your return. Thanks, Piper