Scan failed: A connection attempt failed because --- Client Push Install

[ahayz33]

I select the ip's and click scan.

No matter what credentials or ip's I select for outside my building I get this error.

 

Scan failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

 

 

I am thinking it must be a firewall issue blocking this but I don't see it in the logs as being blocked.
 

[Rsullinger]

Hey Ahayz93,

 

It could be a prerequisite issue as well. Just to make sure, confirm if one of the clients you are trying to scan has these items checked:

 

The following prerequisites must be met for all Managed Clients using the Malwarebytes Management Console:

• .NET Framework 3.5 or higher
• Windows Installer 4.0 or higher
• File and Printer enabled
• NetBIOS enabled
• Network Discovery enabled

If that does not do it, is the IP range you are trying to scan part of your domain or are they public IP's? If the prerequisites do not end up being the case, we may need to open a ticket so I can have you gather some logs for us to review.

 

Thank you,

 

Ron S

[ahayz33]

The ip's are on a different domain but I put the credentials in and they still won't scan.  Pre reqs appear to be all met. 

[Rsullinger]

Hey Ahayz33,

 

No problem. This is something I would want to collect some logs on to see where the issue may be. Do you mind sending me a PM with your e-mail address so I can create a ticket for this?

 

Thank you,

 

Ron S

[ChrisC]

We are having the same issue with (what sounds like) a similar situation. Were you ever able to resolve this? 

[celee]

On 5/11/2016 at 2:24 PM, ChrisC said:

We are having the same issue with (what sounds like) a similar situation. Were you ever able to resolve this? 

Hi @ChrisC, please create a support ticket here: https://www.malwarebytes.org/support/business/#techhelp and one of our support agents can assist you via email. 

Thanks,

Cecile

[Caleos]

I am having the same issues. This even happens on clients that have already had the client installed. I have opened a support ticket but have not received a response.

8/2/2016 3:01:05 PM","admin","127.0.0.1","System",5008,"[10.10.10.205]: Scan failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.","COAMALWARE"
 

 

Alan

[Laurente]

I'm having also the same problem, i tried many solution but still without issue. Please refer us to topic that can arrange this for us. Thanks a lot.

[ahayz33]

I ended up having to make sure to check box the WMI during push, also had to use workgroup\  for login.

[Laurente]

Does it seems to be practical ahayz33? The results are expected?

[jpereboom]

I am also having this issue.  

[jpereboom]

It does see the computers when trying to deploy to them.  However I get the error on all 4 of them "WB-RBENSON" [172.16.30.101]: Scan failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[jpereboom]

Support said that Windows Update KB 3161949 may be an issue.  I uninstalled this update and it fixed my issues. 

[mcingolani]

Hi, 

This is Mike from the Business Team, If you are still seeing this issue please open a ticket with us here:

https://www.malwarebytes.com/support/business/#techhelp

Please include any errors, screenshots or logs that you have. As stated above, one cause we have found may be the latest  KB 3161949  Windows Update that hardened NetBios, so if the clients are on a different subnet, they will not be seen. 

Thanks again and have a good weekend.

[jpereboom]

Mike,

  Thanks for the response.  The support team assisted me with this and is now resolved. Uninstalling KB 3161949 was the resolution for me.  They also said I could do the following in lieu of uninstalling the entire KB. 

. It's also possible to enable the functionality of NetBIOS to the previous state without having to uninstall the whole KB. 

Following the bit from Microsoft.

###

After you install this security update, the following changes are applied:
NETBIOS communication outside of the local subnet is hardened. Therefore, by default, some features that depend on NETBIOS (such as SMB over NETBIOS) will not work outside the local subnet. To change this new default behavior, create the following registry entry:
SUBKEY: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
Value Name: AllowNBToInternet
Type: Dword
Value: 1
Default value of the flag: 0

[mcingolani]

Hi, 

 

Thanks for the update and glad it is working well for you now.