Jump to content

Win7 Machines can't connect to network


Recommended Posts

All of our win7 machines are still having issues from the bad dat.  Rebooting doesn't search for new dats, trying to ping out on the affected machines receives general failure responses.  We're running anti malware and anti exploit.  The only solution seems to be to disable the malwarebytes services, after restarting them have same issue and it never updates.  db info = 2018/01/27 10:30:31 -0500, think some also have an 11:57 one that doesn't work as well.  

All of the other solutions seem to say reboot/update fixes it, but not on ours.  If we hit check for updates it says it's at the latest version.  I've also told the clients (offline) to update.  We're running on premise management console not a cloud version. 

Link to post
Share on other sites

  • Staff

We're sorry you had issues with our program today. We've addressed the issue and here's what you need to do to fix it.

Malwarebytes Endpoint Security (on-premises)

First step to get the update is to disable the real-time protection. To do this in the Management console:

  1. Open up the policy the clients are on and go to the protection tab.
  2. From here, disable the ‘enable protection module’ option.
  3. Once this is done click OK. When your clients check in they will get this new policy update.
  4. Once real-time is protection is disabled and your clients can communicate, highlight the endpoints on the client screen and click the update database button at the top.
  5. After the update is applied, a reboot of the machine may be required.

Note: If your client cannot resolve internal addressing, then re-installing the agent manually on the machine will need to be done. The client will not be able to reach out to the server for a policy update and will never be able to turn off the real-time protection.

To learn more about what happened, please go here: 

If the above doesn’t resolve the issue, please reach out to support at corporate-support@malwarebytes.com

Link to post
Share on other sites

Quote

Note: If your client cannot resolve internal addressing, then re-installing the agent manually on the machine will need to be done. The client will not be able to reach out to the server for a policy update and will never be able to turn off the real-time protection.

So if the Malwarebytes mess up hit thousands of clients across multiple locations causing them to be unable to resolve internal addressing we will now have to manually go and fix Malwarebytes on every machine in our environment before business starts up again on Monday?

Edited by Thrawn
Link to post
Share on other sites

Same situation as above... Reboot works on Win10 but Win7 is General Failure on ping etc.

Any progress or workarounds? It seems we can ping some of these broken endpoints as they appear to be blocking egress locally. Maybe a powershell script to remove previous DB files? Please let me know what and how you are fixing from enterprise level versus manual.

 

Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.