Avast WEBforum
Business Products => Avast Business => Cloud Management Console & Clients => Topic started by: RichardEb on July 30, 2018, 01:27:47 PM
-
Hello,
I'm using Avast Business Manages (cloud hosting). At the moment none of my clients can retrieve (definition) updates. I allways get the error "DNS Resolve has failed".
Any Ideas? Which URL ist Avast resolving there? (If you can give me the url I can check my dns Server for problems). But any other DNS Requests work properly.
Thx
-
I am having the same issue. All of my machines are unable to pull updates from the server with the "DNS resolve has failed" error.
-
Same issue here.
-
Hi,
We are receiving many reports of this from On-premise and Cloud based console installs.(with or without local update mirror/master agents)
Can we speedily resolve?
-
We are using cloud based management console and already tested with and without local update mirror.
Problem also seen at multiple multiple sites (we are IT solution provider and installed Avast Business at multiple customer's sites).
Best regards.
-
Ditto.
Some of our customer installations seem to work fine. But others are suffering from the DNS Resolve has failed problem. This is despite changing DNS servers to Google's DNS to see if this worked (it didn't). Reinstalling on one Windows 10 machine has worked. But reinstalling on a Windows Server 2012 computer didn't.
Looking forward to a resolution...
-
Hi guys, I forwarded it. Let's see...
-
Can you, please, generate support package and send us package ID? How to generate support package can be found at
https://support.avast.com/cs-cz/article/Submit-support-file https://support.avast.com/en-ww/article/Submit-support-file (thanks Asyn)
-
Can you, please, generate support package and send us package ID? How to generate support package can be found at https://support.avast.com/cs-cz/article/Submit-support-file
English version: https://support.avast.com/en-ww/article/Submit-support-file
-
I've been seeing this same issue for the best part of 2 weeks now on my entire estate with Avast Business Cloudcare.
Several conference calls with Avast 2/3 tier (when they're not a. Not in at the time we've been told to call or b. On vacation!!!!!) via our re-seller and the best they can come up with - "it's your DNS".
I'd post my reply to that - but it is unprintable in polite language. I'm also going to forward a link to this topic to my re-seller. It might help them focus their anger on Avast when the revenue stream from us is terminated because Avast have broken something and refuse to even admit they have a problem.
-
Same issue for the last two weeks, cloud 900 users. Please just fix it avast just moved over to Avast come on Avast.
-
Also seeing this since June. I am looking for a refund for all the time that was paid for and protection defunked. This is not ok, this needs to be addressed ASAP. This is not business class.
-
Unless we see your specific support package, we cannot say if it is the same issue. When avast cannot get package with one method it tries another cycling IPv4 and IPv6 and http and https and using curl and winhttp. Messages in the log might be misleading. For instance some hosts do not resolve to IPv6 (intentionally) and such retry is always logged. If your log looks like snippet below, problem is with highlighted lines, remaining stuff in the log (DNS resolving) is just consequence that avast could not connect to server. We are continuing investigation and once we know more we will let you now.
[2018-07-13 02:32:38.193] [warning] [settings ] [ 4672: 3904] Did not find any values in file 'C:\ProgramData\AVAST Software\Avast\burger_client.ini'
[2018-07-13 02:32:39.865] [error ] [Ares ] [ 4672: 3064] Unable to resolve hosts after 1671 ms (258, ?)
[2018-07-13 02:32:39.880] [info ] [servers ] [ 4672: 3064] 'http://w3072800.iabs.u.avast.com/iabs' with [62.245.136.56] chosen for 'program'
[2018-07-13 02:33:01.084] [error ] [Curl ] [ 4672: 3064] 'http://w3072800.iabs.u.avast.com/iabs/servers.def.vpx' from [62.245.136.56] was not downloaded (12007, Couldn't connect to server)
[2018-07-13 02:33:01.084] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to WinHttp IPv4
[2018-07-13 02:33:03.084] [info ] [servers ] [ 4672: 3064] 'http://d3831337.iabs.u.avast.com/iabs' with [62.245.136.56] chosen for 'program'
[2018-07-13 02:33:24.099] [error ] [WinHttp ] [ 4672: 3064] 'http://d3831337.iabs.u.avast.com/iabs/servers.def.vpx' from [62.245.136.56] was not downloaded (12002, ?)
[2018-07-13 02:33:24.099] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to Curl IPv6
[2018-07-13 02:33:26.099] [warning] [servers ] [ 4672: 3064] There is no suitable url for 'program' with IPv6 and http
[2018-07-13 02:33:26.099] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to WinHttp IPv6
[2018-07-13 02:33:29.771] [error ] [Ares ] [ 4672: 3064] Unable to resolve hosts after 1671 ms (258, ?)
[2018-07-13 02:33:29.771] [warning] [servers ] [ 4672: 3064] There is no suitable url for 'program' with IPv6 and http
[2018-07-13 02:33:29.771] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to Curl IPv4
-
You'll be contacted by technical support representatives in order to get debug log files.
-
In my case I see "DNS resolve has failed" only for machines which are placed under Group with "Always update from Avast servers" checkbox is clear.
But after that failure error display updates are being pulled from Local Update server (located by IP address), you can see the screenshots in attached screenshots.
I guess "DNS resolve has failed" relates to failure to resolve Local Update server hostname.
When "Always update from Avast servers" checkbox is checked, then no DNS resolve error is displayed and updates are pulled only from Internet.
-
Unless we see your specific support package, we cannot say if it is the same issue. When avast cannot get package with one method it tries another cycling IPv4 and IPv6 and http and https and using curl and winhttp. Messages in the log might be misleading. For instance some hosts do not resolve to IPv6 (intentionally) and such retry is always logged. If your log looks like snippet below, problem is with highlighted lines, remaining stuff in the log (DNS resolving) is just consequence that avast could not connect to server. We are continuing investigation and once we know more we will let you now.
[2018-07-13 02:32:38.193] [warning] [settings ] [ 4672: 3904] Did not find any values in file 'C:\ProgramData\AVAST Software\Avast\burger_client.ini'
[2018-07-13 02:32:39.865] [error ] [Ares ] [ 4672: 3064] Unable to resolve hosts after 1671 ms (258, ?)
[2018-07-13 02:32:39.880] [info ] [servers ] [ 4672: 3064] 'http://w3072800.iabs.u.avast.com/iabs' with [62.245.136.56] chosen for 'program'
[2018-07-13 02:33:01.084] [error ] [Curl ] [ 4672: 3064] 'http://w3072800.iabs.u.avast.com/iabs/servers.def.vpx' from [62.245.136.56] was not downloaded (12007, Couldn't connect to server)
[2018-07-13 02:33:01.084] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to WinHttp IPv4
[2018-07-13 02:33:03.084] [info ] [servers ] [ 4672: 3064] 'http://d3831337.iabs.u.avast.com/iabs' with [62.245.136.56] chosen for 'program'
[2018-07-13 02:33:24.099] [error ] [WinHttp ] [ 4672: 3064] 'http://d3831337.iabs.u.avast.com/iabs/servers.def.vpx' from [62.245.136.56] was not downloaded (12002, ?)
[2018-07-13 02:33:24.099] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to Curl IPv6
[2018-07-13 02:33:26.099] [warning] [servers ] [ 4672: 3064] There is no suitable url for 'program' with IPv6 and http
[2018-07-13 02:33:26.099] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to WinHttp IPv6
[2018-07-13 02:33:29.771] [error ] [Ares ] [ 4672: 3064] Unable to resolve hosts after 1671 ms (258, ?)
[2018-07-13 02:33:29.771] [warning] [servers ] [ 4672: 3064] There is no suitable url for 'program' with IPv6 and http
[2018-07-13 02:33:29.771] [warning] [dldwrap ] [ 4672: 3064] HttpGet: download type switched to Curl IPv4
I sent my support package over a week ago and I am yet to hear anything from Avast. How widespread is this issue? What is the ETA on a fix?
-
Any update on this matter?
A solution must be speedily created as a lot of our clients are looking elsewhere for AV solutions from competitors
-
We're still not able to reproduce the issue locally in case of Avast Business Managed Antivirus. We found an issue in Mirror which caused similar problems in AV managed by CloudCare or Managed Workplace. From all the support packages we got is still unclear what is wrong.
Could you please try to download the following file manually on the device where the resolution failed
http://w3072800.iabs.u.avast.com/iabs/servers.def.vpx
Could you please also try traceroute following URL/IPs and share a result with us?
tracert w3072800.iabs.u.avast.com
tracert 8.8.8.8
tracert 8.8.4.4
-
I'm having this same issue across multiple client systems in different offices. All other DNS functions are fine. All of my clients are managed through CloudCare and all are on 4.3.1.
My test machine currently does have the "DNS Resolve Failed" issue but can download the server.def.vpx file below with no issue.
tracert info: Local IP addresses removed
Tracing route to a428.dscd.akamai.net [184.27.199.33]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxxxx
2 9 ms 9 ms 3 ms xxxxxxxx-static.hfc.comcastbusiness.net [xxxxxxxx]
3 31 ms 29 ms 29 ms 96.120.14.37
4 17 ms 11 ms 21 ms ae-222-rur01.sacramento.ca.ccal.comcast.net [68.87.203.69]
5 26 ms 31 ms 19 ms ae-2-ar01.sacramento.ca.ccal.comcast.net [162.151.18.133]
6 28 ms 20 ms 19 ms a184-27-199-33.deploy.static.akamaitechnologies.com [184.27.199.33]
Trace complete.
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxxxxxxxxxxx
2 2 ms 5 ms 1 ms xxxxxxxxxxxx-static.hfc.comcastbusiness.net [xxxxxxxxxxxx]
3 28 ms 27 ms 29 ms 96.120.14.37
4 28 ms 29 ms 29 ms ae-222-rur01.sacramento.ca.ccal.comcast.net [68.87.203.69]
5 16 ms 29 ms 19 ms ae-2-ar01.sacramento.ca.ccal.comcast.net [162.151.18.133]
6 24 ms 29 ms 29 ms be-33667-cr01.9greatoaks.ca.ibone.comcast.net [68.86.93.25]
7 30 ms 29 ms 30 ms be-12578-pe04.9greatoaks.ca.ibone.comcast.net [68.86.88.18]
8 23 ms 39 ms 29 ms 96-87-8-246-static.hfc.comcastbusiness.net [96.87.8.246]
9 * * * Request timed out.
10 30 ms 25 ms 19 ms 108.170.237.104
11 27 ms 29 ms 39 ms 108.170.232.61
12 26 ms 29 ms 29 ms google-public-dns-a.google.com [8.8.8.8]
Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxxxxxxxxxxxx
2 3 ms 9 ms 3 ms xxxxxxxxxxxxx-static.hfc.comcastbusiness.net [xxxxxxxxxxxx]
3 27 ms 29 ms 19 ms 96.120.14.37
4 17 ms 19 ms 21 ms ae-222-rur01.sacramento.ca.ccal.comcast.net [68.87.203.69]
5 11 ms 28 ms 23 ms ae-2-ar01.sacramento.ca.ccal.comcast.net [162.151.18.133]
6 23 ms 30 ms 28 ms be-33667-cr01.9greatoaks.ca.ibone.comcast.net [68.86.93.25]
7 21 ms 29 ms 22 ms be-12544-pe01.9greatoaks.ca.ibone.comcast.net [68.86.87.150]
8 28 ms 29 ms 23 ms fonality-cr01.losangeles.ca.ibone.comcast.net [75.149.228.74]
9 * * * Request timed out.
10 25 ms 29 ms 40 ms 209.85.248.34
11 26 ms 29 ms 29 ms 209.85.142.235
12 17 ms 29 ms 28 ms google-public-dns-b.google.com [8.8.4.4]
Trace complete.
-
Hi jetcosys,
please, could you upload technical support package and write here back the package id? There is a link how to do it: https://support.avast.com/en-ww/article/Submit-support-file
Thank you in advance
-
In response to:
Aleksandr Nazaryan - "When "Always update from Avast servers" checkbox is checked, then no DNS resolve error is displayed and updates are pulled only from Internet."
That is NOT an acceptable answer for anything more than an estate of a few machines.
Mine is pretty small at 32, others are hundreds. You really, REALLY don't want all of those going to the internet individually for their updates.
What the hell is the point of assigning "update agent" machines then? NONE!
BTW - I've noticed that a relatively new "behaviour" with my cloud care is that the update agents I've assigned for each subnet keep being cleared! Why?
Is this Avast's ham-fisted attempt to try and keep updates going while they figure out what is broken in UpdateProxy.dll?
-
We're still not able to reproduce the issue locally in case of Avast Business Managed Antivirus. We found an issue in Mirror which caused similar problems in AV managed by CloudCare or Managed Workplace. From all the support packages we got is still unclear what is wrong.
Could you please try to download the following file manually on the device where the resolution failed
http://w3072800.iabs.u.avast.com/iabs/servers.def.vpx
Could you please also try traceroute following URL/IPs and share a result with us?
tracert w3072800.iabs.u.avast.com
tracert 8.8.8.8
tracert 8.8.4.4
On our clients the file can be downloaded, and tracing the host and IPs works like a charm.
We need a solution immediately, or we need to recommend anti-virus software from other manufacturers to our customers in the future.
That is not satisfying!
-
Hello, I read log snippet as there is 20s timeout reached for connection to our servers (specifically http://w3072800.iabs.u.avast.com/iabs/servers.def.vpx served by 62.245.136.56). The content is present on the server so I can only point to some networking issue.
-
Hello.
Are you saying that all of our Avast Business Cloud installations happen to have the same problem at about two dozen of our customers, with different network configurations, firewalls, and ISPs?
In addition, other customers here in the forum have the same unexplainable problem? Sorry, that does not seem realistic to me.
I am expert in IT networking and infrastructure. All of our above mentioned customers only have this problems with Avast update mechanisms and only since "upgrading" it from Avast Endpoint Security, while upgrading means that we did fresh installations without importing old settings automatically.
If pointing to others shows the kind of support that Avast will offer to its customers in the future, then we will have to use products from other manufacturers for our customers in the future. This is not the quality of software we can represent.
Best regards.
-
Any solution yet?
-
Any update? Same issue here.. >:( >:(
-
I removed alle Master Agents. Now most of the Workstations are updating again. Looks like a Problem with the Master Agent concept itself. Maybe in relation with the DNS-Services of a Domain-Controler? Anyway: disabling the Master Agent isn't a real solution.
What me really bothers is that: Why don't the Workstations switch to online update if they can't reache the Master Agent? This looks like a desing failure to me
-
Wireshark dump of failed update might be interesting to see.
-
We are testing fixes on both P1 issues with CloudCare and AfB update mirrors. We will post here again when we get ETA for the release.
-
You may want to add a fallback also: If an update via Master Agent fails, a direct online update should be performed. A Master Agent could be unreachable for several reasons. But an up to date client is essential.
-
You may want to add a fallback also: If an update via Master Agent fails, a direct online update should be performed. A Master Agent could be unreachable for several reasons. But an up to date client is essential.
Absolutely. Fallback update method will get fixed as well.
-
We're having the exact same issues on a few customers' networks. Avast seems to be interfering with local DNS queries. Even if the computer only has a local DNS server in it's configuration it's still getting DNS requests from external servers. This, of course, is causing Active Directory issues.
-
I updated my Avast this morning, and immediately had a DNS service error. Since it was ONLY affecting 1 device, I used system restore, and restored to a previous state. The system restore was successful, and I was back online. I then created a new restore point, and updated Avast. Once again, I had a DNS server error. I will update Avast as soon as I know this problem with the update is fixed.
My advice - restore your system to a restore point created PRIOR to the Avast update. This should get you back online, until Avast fixes this bug.
Edited to add the File ID created by the Avast Support tool: B1495
-
Hello, I want to inform you that we are preparing uUpdate containing fix of the issues with DNS for AV 18.5 that caused problems with detection of the mirror server.
Unfortunately, part of the fix is also in the CloudCare agent, which hasn't been approved by their QA yet and the problem with the fallback is in the code of setup, which can't be updated by uUdpdate at all. So the issue should be completely solved in the AV 18.6, which we are releasing at the beginning of September.
Thank you for your patience
-
Thanks Libor, at least we've a timeframe now...
-
Hello, we are in the final phase of testing the uUpdate. It'll be released in few days.
-
When an update/fix will be available???? it's already September!!!!!
Currently, we got over 40 machines that unable to update definition since last month...This is unacceptable... >:(
-
We need the update ASAP
-
This is happening to us too! Is there a solution?
-
Any time-frame we can give clients on release of 18.6 and console 6?
Many clients have started trials of competitor AV vendors. It is very frustrating dealing with daily complaints about mirror updates failing and not being able to give a clear answer. We seem very unprofessional and I agree with clients.
Please Avast, we are losing lifelong avast clients like wild fire. Customers ranging from 5 to 3600 seat licenses.
-
Hi,
I'm really sorry to hear about the problems, but the promised uUpdate fixing this issue in AV 18.5 (at least at our side) was released at the end of August. You can try to check content of the key named "MicroUpdates" in "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AVAST Software\Avast" path of your registry. You should find uUpdate number 377=unixtime placed here, if it was already updated.
Unfortunately, this uUpdate doesn't fix the issue in the UpdateProxy.dll in case that you use CloudCare and also the problem with downloading from avast servers in the setup (if mirror is unavailable). However, it should help you with the downloading issue if you use the managed Avast Business Antivirus.
Regarding the AV 18.6 and console 6 which contain all the fixes included: we are finalizing tests of the console 6.0 together with AV 18.6, however, we need to synchronize the testing with the CloudCare and Managed Workplace team. I'm really sorry but I can't tell you any specific date at the moment as we are dependent on the other teams, but I hope it will be soon.
-
So much of lying to clients >:( >:( ... Your support was promising us for early Sept. 2018 release and now you cant even give us a date. >:( >:( >:(
Lesson learned .. never trust AVAST as a company or even as a forum member >:( >:(
-
Any time-frame we can give clients on release of 18.6 and console 6?
Many clients have started trials of competitor AV vendors. It is very frustrating dealing with daily complaints about mirror updates failing and not being able to give a clear answer. We seem very unprofessional and I agree with clients.
Please Avast, we are losing lifelong avast clients like wild fire. Customers ranging from 5 to 3600 seat licenses.
Hi... Since AVAST become a joke ..can you please help us with any recommended competitor AV vendors?
you can send me the details on my personal email: kabooos-28@hotmail.com
many thanks friend 8)
-
Still no solution? Is Programversion 18.5.2535 the latest one? Any possibility to download and install the latest signatures manually, eg via hyperlink?
-
this is a completely f*** up way of dealing with an update fixed from a company with a bunch of software engineers/departments who don't communicate between themselves to address this issue ASAP!!!!!!!
-
Any possibility to download and install the latest signatures manually, eg via hyperlink?
https://www.avast.com/download-update
-
Thx, Infratech Solutions, this was helpful.
-
Am also getting this issue. Strangely only affecting the minority, haven't found a quick fix as of yet.
-
Is this issue fixed with new version 18.6.2349?
How to install:
1. Update from your existing Avast version via Settings -> Update -> Update program
2. Or you can download and install from here
Online installers (recommended):
http://files.avast.com/iavs9x/avast_free_antivirus_setup.exe
http://files.avast.com/iavs9x/avast_internet_security_setup.exe
http://files.avast.com/iavs9x/avast_premier_antivirus_setup.exe
Offline installers:
http://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe
http://files.avast.com/iavs9x/avast_internet_security_setup_offline.exe
http://files.avast.com/iavs9x/avast_premier_antivirus_setup_offline.exe
We hope you enjoy the new version!
AVAST Team
1. Update from your existing Avast version via Settings -> Update -> Update program won't work -> DNS resolve has failed...
2. Or you can download and install from here -> in this case, what happens with the actual settings?
-
Is this issue fixed with new version 18.6.2349?
Hi Christoph, that's the consumer version/product.
Business: https://forum.avast.com/index.php?topic=221805.0
-
Hi,
This issue has been fixed in version 18.6. This version will be widely distributed to all client devices on the 17th September.
If you require 18.6 on the devices now to resolve the issue, you can uninstall 18.5 version, download 18.6 from the console and deploy to those devices.
Regards,
Sean
-
In console is still old version 18.5.
-
Hi,
This issue has been fixed in version 18.6. This version will be widely distributed to all client devices on the 17th September.
If you require 18.6 on the devices now to resolve the issue, you can uninstall 18.5 version, download 18.6 from the console and deploy to those devices.
Regards,
Sean
WTF, who has time to uninstall and reinstall for 50 machines or so???? You? if so, then you got too much damn free time on your hands...
the fact the matter is that this should have been fixed weeks ago, not until next week or so.
-
A new version of Avast Business Managed Antivirus is scheduled for release on September 17th, 12:00 UTC.
Since September 10th the version 18.6 has been available for new installations only. Starting this rollout your AV will be updated automatically in following few days (according to your settings).
*Note: a restart of the workstation may be required.
-
Is there any update on the rollout? I've just reinstalled. Console is on 6.x but clients (even after a new download, both offline and online) are still on 18.5.2535
-
Still unable to update. DNS resolve has failed. Host unreachable.
Over 120 PCs with out of date (18.5.2535) cloudcare business in my environment!
-
Didn't even realize I was having this issue until I wondered why my mail server was dragging a bit (was a bit out of date). I did have to uninstall the aVast business antivirus / agent components out of add/remove programs for 18.5 and reinstall on my management server using the on-premise console (6.0.8). I also use that machine as my master agent / local update host which had to be redone, but once there the other machines seemed to filter through. Didn't have to reinstall the management console at least.
-
Same problem here.
We just moved to Avast Antivirus Business Managed and I was implementing the Avast Master Agent and then when i force update in a client it looks like it can't find the local update server(DNS resolving error) and ends up by doing updates from the Avast servers, so it's not working!
-
I've updated ~25 clients to the version 18.6...
Still same error (DNS resolving error) via local mirror C:\ProgramData\AVAST Software\Persistent Data\Avast\Logs:
https://pastebin.com/raw/SZZ8yVf1
Now had no idea how to fix it...
And how I've empty entry '' for IP\DNS in mirror's setting file even after full client reinstall?
C:\Program Files\AVAST Software\Avast\setup\smbupd.def:
[servers]
maintenance=0
count=1
override=0
[mirror]
enable=0
allow_fallback=1
[server0]
name=Download Mirror ABS Server 0
urlpgm=http://:4158/iabs
urlpgmcc=http://:4158/iabscc
urlpgmmw=http://:4158/iabsmw
urlvps=http://:4158/ivps9x
urlvpslitenitro=http://:4158/vpsnitrotiny
urlvpsnitro=http://:4158/vpsnitro
Any help?
-
Hi Assist2,
I'm sorry you are still having an issue with the mirror server, we thought that the bug is already fixed with the release of AV 18.6.
Firstly, please, could you check that the station is really available via. "ping" and "tracert" to the mirror server?
Secondly, please, could you enable the debug logging, restart the "Avast Business Console Client" service and send us the log files after the content of smbupd.def is newly overwritten?
Thank you in advance
-
Secondly, please, could you enable the debug logging, restart the "Avast Business Console Client" service and send us the log files after the content of smbupd.def is newly overwritten?
Thank you in advance
Where is the setting to activate debug logging on Client?
When the content of smbupd.def overwrittening? Every time I click Update in Client?
-
Assist2:
Enable debug logging is an option in the settings in the console (it's present in the "Troubleshooting" section) and also in the AV settings ("Settings -> General" in the "Maintenance" section). Personally, I would recommend to set it manually directly in the AV.
The content of smbupd.def is overwritten after the application of the policy/settings, i.e. if you turn off the "Avast Business Console Client" service, enable the debug logging and turn the mentioned service on then it should be after several minutes at most.
-
Assist2:
Enable debug logging is an option in the settings in the console (it's present in the "Troubleshooting" section) and also in the AV settings ("Settings -> General" in the "Maintenance" section). Personally, I would recommend to set it manually directly in the AV.
The content of smbupd.def is overwritten after the application of the policy/settings, i.e. if you turn off the "Avast Business Console Client" service, enable the debug logging and turn the mentioned service on then it should be after several minutes at most.
Where should I search the log file?
Does it in C:\ProgramData\AVAST Software\Avast\log\?
-
Yes, "c:\ProgramData\AVAST Software\Avast\log" is the correct place with the logs inside. I would also suggest adding content of "c:\ProgramData\AVAST Software\Avast\var".
Thank you in advance
-
I came into work today and noticed that our Avast clients were updated from 18.5.2535 to the 18.6.2540!
Here I was thinking that I'd need to manually touch all our machines to reinstall, since just running the update .exe didn't do anything...
Thanks for letting me keep my weekend Avast
-
Hi Assist2,
I'm sorry you are still having an issue with the mirror server, we thought that the bug is already fixed with the release of AV 18.6.
Firstly, please, could you check that the station is really available via. "ping" and "tracert" to the mirror server?
Secondly, please, could you enable the debug logging, restart the "Avast Business Console Client" service and send us the log files after the content of smbupd.def is newly overwritten?
Thank you in advance
Somehow after a few days at 18.6 everything is works fine
Thanks!
-
Anyone else still having problems with the local premise business console local update server not working?
We are using the on premise business console, version 6.0.14.951 and have 80 windows clients. The system is configured to pull updates from the local server (192.168.100.19) but it has never worked. I upgraded our console from 6.0.8 today in the hopes of resolving this, but no. Still no updates from local update server.
Antivirus software version on both server and clients is 18.8.2546 (build 18.8.4084.409).
Server replies to ping by name as well as IP so there is NO DNS ISSUE LOCALLY. Server firewall has appropriate ports open. Tested with server firewall disabled, still no updates from local update server.
Contents of workstation smbupd.def file is:
[mirror]
enable=1
allow_fallback=1
[servers]
maintenance=0
count=1
override=1
[server0]
name=Download Mirror ABS Server 0
urlpgm=http://192.168.100.19:4158/iabs
urlpgmcc=http://192.168.100.19:4158/iabscc
urlpgmmw=http://192.168.100.19:4158/iabsmw
urlvps=http://192.168.100.19:4158/ivps9x
urlvpsnitro=http://192.168.100.19:4158/vpsnitro
urlvpslitenitro=http://192.168.100.19:4158/vpsnitrotiny
Any input would be most appreciated! I opened a ticket with tech support, but honestly I am not very hopeful. Having 80 clients constantly checking / updating antivirus via the internet is just crazy and uses way too much bandwidth.
Thanks
-
Take a look at Avast Business Managed Troubleshooting Guide (https://kb.support.business.avast.com/GetPublicArticle?title=Avast-Business-Management-Console-Troubleshooting-Guide)
-
Thanks for the quick response. I went through the Avast Business Managed Troubleshooting Guide. On the client I did see some bcc event log errors referencing the server IP and port 8088. There was no firewall rule specifically for port 8088, nor do I see it in any documentation anywhere either. Not sure if that is left over from a legacy install or what. Anyway I added a firewall rule on the server & tested from client - still not updating. Disabled server firewall & tested from client - still not updating.
There IS communication from the management console to the clients as config changes are propagated to the clients with no problem. The clients are simply not getting definition and program updates from the local server.
Stopped client services, deleted C:\ProgramData\Avast Software\Avast\afb & C:\ProgramData\Avast Software\Avast\var folders. Restarted services, still not updating...
Regards,
Todd
-
Thanks for the quick response. I went through the Avast Business Managed Troubleshooting Guide. On the client I did see some bcc event log errors referencing the server IP and port 8088. There was no firewall rule specifically for port 8088, nor do I see it in any documentation anywhere either. Not sure if that is left over from a legacy install or what. Anyway I added a firewall rule on the server & tested from client - still not updating. Disabled server firewall & tested from client - still not updating.
There IS communication from the management console to the clients as config changes are propagated to the clients with no problem. The clients are simply not getting definition and program updates from the local server.
Stopped client services, deleted C:\ProgramData\Avast Software\Avast\afb & C:\ProgramData\Avast Software\Avast\var folders. Restarted services, still not updating...
Regards,
Todd
I have the same problem.
Can you download these files on the client from the local update server?
http://IPupdateServer:4158/iabs/servers.def.vpx
http://IPupdateServer:4158/iabs/prod-pgm.vpx
-
Hello, same problem here, with pc's with no restrictions to accessing the internet and it gives an error of Host unreachable, you must have problems with your servers!
-
Well it looks like Avast has done something, today the updates started to work as normal again, and we haven't change anything on our side.
-
Well it looks like Avast has done something, today the updates started to work as normal again, and we haven't change anything on our side.
I'm glad your issue has been resolved. Let us know if you continue to experience any issue.