I’m having an issue with a new install of Avast Business Protection. Most of the PC’s on my LAN show as “disconnected”. The Admin console was able to discover them and remote install the Avast Client but after that they only show as “Disconnected”.
Windows (or any other) firewall is disabled. They PC’s are powered on and I can ping them from the admin console PC.
I have the same problem. Server is 2008 R2 and clients are XP-Win7. Firewall is turned off by GP. Initially the clients showed up as connected but now all but the server itself are disconnected. The logs show they are connecting but the status does not reflect this.
I also experience this issue. It appears that many clients bounce from online to offline status based on each poll. Is there a way to loosen the polling criteria?
I’m having this problem regularly too. Restarting the administration console service “fixes” it, but since it happens at least once almost every day, I’d guess there is something wrong in the code. Maybe it should watch the connected computers and when none have connected in a reasonable time, automatically restart itself (or close and re-open the ports or something to try to resolve the issue).
I have 125 clients in two different subnets, and almost 100% of the clients show disconnected. I like others restart the Console and the clients appear and then as usual simply disconnect after a short while. I am running the latest Console and the latest client, but the problem persists.
It appears this is a known issue and has been for sometime know, but I do not see any kind of response from Avast concerning this issue. Is this leaving our clients unprotected, if a client becomes infected how will we know since they are consistently disconnected, even though they are indeed online.
I like the product, and once again stuck my neck out to keep it at our facility, but I am loosing confidence since they do not seem to acknowledge (at least I cant find it) and they haven’t fixed the issue. So if someone actually knows what is going on or if they have fixed it and I am simply not seeing the fix – please enlighten me. If there is no supported fix, then my question is – when will there be?
I have this same issue. I am hoping to upgrade from pro v4, but my test install of BP only shows 1 of my test installs in the console. The one that works is a 2003 server, the other two are XP and W7 64bit. The working one had no AV previously, the other two had v4 pro removed first.
Sorry for the delay – had to many projects in the fire and have simply dealt with the disconnect issues manually. If you tell me how to generate the report you are asking for I will be happy to generate and send it along.
Open your Administration console and click on Admin in the left column. Then click on Setting and choose Troubleshooting. You will see the button to Download Troubleshooting package that contains the log files.
We seem to have been experiencing something similar for the last couple of months. Periodically I’ll check the console to make sure everything looks happy, typically like once a week. It seems like every couple of weeks I’ll noticed that while a few clients are still showing connected to the console (green check), there will be a good number of them that I know are online and connected to the netwrok which aren’t showing up as connected - my own laptop from which I am connecting to the console, for instance! It seems that restarting the Console Monitor service, which in turn restarts the Console service, seems to clear things up.
Something I have noticed in doing this is that the Console service’s process memory seems to be about double the normal value when in this state. For instance, before restarting the services, the Console service was running at ~137MB and the Monitor service at ~20MB. After the restart, they are currently at ~66MB and ~14MB, respectively.
I have also noticed that the last couple of times I have connected to the Console, during the last couple of days, there has been a message on the Network page, just above the filter area, indicating that a node was trying to connect but wasn’t able to and asking if I wanted to fix this problem. Clicking that fixed it but I wasn’t sure if this was related or not. One of those cases was a new node on the network which had just had Avast installed, the other was an existing node which had to be restored from three week old backup because of a driver issue which rendered the machine unusable.
Thoughts, comments, and suggestions happily accepted!