Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on August 13, 2015, 07:08:28 PM
-
Hi
My Avast says I'm protected, but it does say that Secure DNS cannot run on my network. This happened after installing Win10. How do I solve this?
Furthermore, after installing Win10 Avast told me that there was a problem with AvastSvc.exe and I should check if the firewall blocked it. How do I check this? And is Windows Firewall and Avast Firewall compatible in Win10?
Please answer all three questions. Thank you :-)
/Jakob
-
And is Windows Firewall and Avast Firewall compatible in Win10?
I assume windows firewall is compatibel with there own product windows10 ;D and so is avast firewall ;)
have you done a couple of reboots after installing win10 ?
still same message?
-
I believe I've found a workaround for this error:
Simply put, if I am not already connected at system boot, and already am finding this error, it will persist even with multiple reboots.
Solution: Connect the system (CAT5 cable) before a cold boot and boot. Seems avast checks and registers the system early in the boot process for Secure DNS, and will only work if this is done this way. Any other way is potluck, may work, may not. Have not checked to see if this works if an automatic wireless connection is made at logon, but suspect this may work also.
No need to be connected after any subsequent start-ups, you can leave the system disconnected if you like.
-
I believe I've found a workaround for this error:
Simply put, if I am not already connected at system boot, and already am finding this error, it will persist even with multiple reboots.
Solution: Connect the system (CAT5 cable) before a cold boot and boot. Seems avast checks and registers the system early in the boot process for Secure DNS, and will only work if this is done this way. Any other way is potluck, may work, may not. Have not checked to see if this works if an automatic wireless connection is made at logon, but suspect this may work also.
No need to be connected after any subsequent start-ups, you can leave the system disconnected if you like.
Hello mchain,
Please, could you be more specific?
I don't understand why i should connect the cat5 cable before the boot if it is already connected. Do you mean "during the boot"?
It seems like this problem started after the last avast upgrade for no reason, since i haven't change a thing in my network.
I already tried to "fix problems" at the control panel but it didn't help.
Hope you can help me.
Best regards
-
Hello I just want to tell you that I have the same problem since 2015-10-03. And have not installed any Windows 10. I´m still using windows 7. There is another thread on this issue if you look after earlier posts from a few days ago on the same subject.
But unfortunally no valid explanation of the problem as far as I can see. Maybe it´s some server issue on the avast side of the connection ? My own concern is if this affects the safety in the safe zone browser so it is safe to use it even if the secure DNS don´t work. And just like you I haven´t done any changes in network settings.
-
Hello
I am also having the same problem. I am running Avast Premier and the same message appears on the Overview page. I have checked on the Settings under Active Protection and it is telling me secure DNS is active. I am well and truly perplexed ::)
I have Windows 8.1.
Any help would be greatly appreciated.
-
Same here. Earlier today when i turned on my computer that message was just there on Avast homepage... "Secure DNS cannot run on this network". But on the settings it says it is on. Hmmmm a friend told me that since i'm using Google's DNS service Avast cant also run its DNS service on my computer. Thing is, why does it say "ON" on the setting, then? And why did that message on the front screen at Avast user interface only came up today when i didn't change ANYTHING in quite some time?
Thanks in advance.
Edit: I'm using Avast Internet Security
-
I posted about this exact issue a few days ago and was told to do an Avast Repair in the control panel. Well I did and (snarky) I have no clue if it's fixed because my AV firewall will not turn on.
??? Now I know it's going through the entire process of doing a clean reinstall. Ugh... wasting time.
-
So... not even a reply even when a nice bunch of users(in my case a PAYING CUSTOMMER) have the same issue going on. Lots of respect from the Avast "team", no doubts. Maybe i'll just stop using it and move on to a more Custommer friendly AV company.
-
I also have the same issue !!
(http://s14.postimg.org/r5o99c7xt/Capture.jpg)
(http://s14.postimg.org/4gz29rqjx/Capture.jpg) (http://postimg.org/image/4gz29rqjx/)
-
I believe I've found a workaround for this error:
Simply put, if I am not already connected at system boot, and already am finding this error, it will persist even with multiple reboots.
Solution: Connect the system (CAT5 cable) before a cold boot and boot. Seems avast checks and registers the system early in the boot process for Secure DNS, and will only work if this is done this way. Any other way is potluck, may work, may not. Have not checked to see if this works if an automatic wireless connection is made at logon, but suspect this may work also.
No need to be connected after any subsequent start-ups, you can leave the system disconnected if you like.
Hello mchain,
Please, could you be more specific?
I don't understand why i should connect the cat5 cable before the boot if it is already connected. Do you mean "during the boot"?
It seems like this problem started after the last avast upgrade for no reason, since i haven't change a thing in my network.
I already tried to "fix problems" at the control panel but it didn't help.
Hope you can help me.
Best regards
If you are already connected at startup with the CAT5 cable connected, then this workaround should already have worked for you. If not working then try the second option below.
Seems if offline for a couple of days will impact whether avast secure dns server will automatically connect to system here as I did see the 'cannot connect dns error' for about two minutes into fresh new boot. After two minutes passed, dns status changed to connected.
Suggest initiating a new manual virus and definitions update and see if dns status changes along with getting newest definitions. That sometimes seems to work as this will force the avast program to connect to the server(s). Worth a try.
-
Ok we are some avast users with the same problem and it seems to have apeared about the same time. None of the so called workarounds works for me anyway. I remember some time ago when it was problem connecting to the avast update servers and that affected people in many different countries. I don´t know if this problem we have now can have something to do with avast servers on their side ? But I find it strange that several people get the same error message at the same time without having done any changes in our network settings. The earlier problem that I refered to took several weeks to fix on the Avast side of the line
and suddenly everything was back to normal. But ofcourse no explanation were given to their users. But comunicating with customers seems not to be the strong side among antiviruscompanies.
-
Reported to Moderators let's see if that get a reply from Avast. :)
-
Reported to Moderators let's see if that get a reply from Avast. :)
Thanks Bob. The problem still persists so any help will be greatly appreciated.
-
Reported to Moderators let's see if that get a reply from Avast. :)
Thanks Bob. The problem still persists so any help will be greatly appreciated.
I have the same problem and would appreciate any help. I've tried the suggestions to fix and they don't work.
Thanks!
-
Reported to Moderators let's see if that get a reply from Avast. :)
Thanks Bob. The problem still persists so any help will be greatly appreciated.
I have the same problem and would appreciate any help. I've tried the suggestions to fix and they don't work.
Thanks!
Thank you once again Bob for coming to rescue. ;) I waited several days before I updated to the new version so the bugs could be worked out. I have come to expect some issues whenever Avast sends out program updates. Looks like I didn't wait long enough this time.
Again, thanks --> they take notice when you help out. :)
-
"Again, thanks --> they take notice when you help out. "
@ streim
Sometimes but not always. :)
-
As I spent a recent two days figuring out how someone from Han Hoi Precision Ind. Co. Ltd. had a local IP address on my network and getting it cleaned up. During that time I found the Secure DNS feature going on-and-off without cause. (not cycling quickly). After everything was cleaned and verified, the Secure DNS feature was on and working. Then a few hours later, it was off again. After verifying I wasn't under attack and everything was stable, it went on again. And now it's off again.
I found the device injected into my network by running the Avast 'Scan for network threats' and if not for that feature, I may have never found the intruder. That said though, the person probably got in because the Secure DNS feature is inconsistent.
If Avast doesn't at least post a response to these concerns soon, I'm going to have to assume they're not so good at this home network security thing.
-
same problem here , on avast premium , seen it because had the 'online content unavailable' bug ... hope it wont open my computer to attacks
-
Hi, i am German. My English is not good
I have the Problem too
I Have a new FritzBox 7490.
And Windows 10 Home, 64bit
Avast Pro Antivirus 2015
Is it a Problem with my Router, Windows 10 or a Avast Problem
(http://abload.de/img/2015-10-08_174822v7sjc.jpg) (http://abload.de/image.php?img=2015-10-08_174822v7sjc.jpg)
-
As I spent a recent two days figuring out how someone from Han Hoi Precision Ind. Co. Ltd. had a local IP address on my network and getting it cleaned up. During that time I found the Secure DNS feature going on-and-off without cause. (not cycling quickly). After everything was cleaned and verified, the Secure DNS feature was on and working. Then a few hours later, it was off again. After verifying I wasn't under attack and everything was stable, it went on again. And now it's off again.
I found the device injected into my network by running the Avast 'Scan for network threats' and if not for that feature, I may have never found the intruder. That said though, the person probably got in because the Secure DNS feature is inconsistent.
If Avast doesn't at least post a response to these concerns soon, I'm going to have to assume they're not so good at this home network security thing.
Thanks for the idea to run a scan for network threats. Mine was fine thankfully and from the report, it looks like the Secure DNS is working even if the main GUI screen says it's not ...
-
Hi, i am German. My English is not good
Is it a Problem with my Router, Windows 10 or a Avast Problem
fairly confident that it's Avast. I checked my router and it's fine and I run Windows 7.
(you're English is much better than my German!) ;)
-
Hi, i am German. My English is not good
Is it a Problem with my Router, Windows 10 or a Avast Problem
fairly confident that it's Avast. I checked my router and it's fine and I run Windows 7.
(you're English is much better than my German!) ;)
Ok, thanks, then i wait for a Update from Avast
-
I found the device injected into my network by running the Avast 'Scan for network threats' and if not for that feature, I may have never found the intruder. That said though, the person probably got in because the Secure DNS feature is inconsistent.
Hi myNameHere,
these two events can hardly have any connection. SecureDNS is a feature that protects your computer by encrypting all DNS traffic and forwarding the DNS traffic to our own servers - this does not affect how intruders get or not get into your network.
We have experienced a short backend outage of the SecureDNS servers several days ago, but the servers are now back on and running.
Lukas.
-
Well if it´s now up and running can you explain why the message persists on the Avast UI ?
You says that avast had problems with the secure DNS server and now it´s up and running so what shall we do when we still have the message ? The problem started 2015.10.03 on my computer is this about the date that your server wasn´t working properly. It would be helpful if that was confirmed . Plus any suggestions to get rid of the message.
-
Hi, i am German. My English is not good
Is it a Problem with my Router, Windows 10 or a Avast Problem
fairly confident that it's Avast. I checked my router and it's fine and I run Windows 7.
(you're English is much better than my German!) ;)
Ok, thanks, then i wait for a Update from Avast
You're most welcome. Hope the fix comes soon!
-
I got same problem here in swe aswell, started yday (or i noticed it yday)
hope to see a answer and fix for it soon.
-
I am also having this issue.
-
I found the device injected into my network by running the Avast 'Scan for network threats' and if not for that feature, I may have never found the intruder. That said though, the person probably got in because the Secure DNS feature is inconsistent.
Hi myNameHere,
these two events can hardly have any connection. SecureDNS is a feature that protects your computer by encrypting all DNS traffic and forwarding the DNS traffic to our own servers - this does not affect how intruders get or not get into your network.
We have experienced a short backend outage of the SecureDNS servers several days ago, but the servers are now back on and running.
Lukas.
I got the same 'intruders' with the name Han Hoi &C. 9 of them to be precise. Apparently now they are gone.How do you explain these?
-
Hello everyone!
I have already tried fixing the Avast in the control panel, tried to boot the computer with and without the ethernet cable, tried to turn the Safe DNS on and off and, looked for new definitions of virus and software update and nothing worked.
Let's try to find something in common between us:
In my case, this problem started after the last software update. Have you guys noticed if it started after this update too?
As i said before, i did not changed a thing in my network.
I'm a Windows 7 Professional user and i'm constantly updating my O.S.
-
I.m using Windows 7 home premium SP 1. My problem started 2015.10.03. Eveything is updated. A member of the Avast team posted that they have had some problem with their secure server but that problem was now solved ? Everything shows green in the Avast UI All shields are up and everything is updated. But still that message apears about the secure DNS server. I was hoping for an answer from the person from the Avast team but still nothing. I´ve tried all the so called solutions, but they made no difference. So hopefully the rest of Avast is working. I have run all the different security checks in Avast pro antivirus and nothing seems wrong. But I just wont to get rid of that message that keeps me wonder about the safety.
-
I have 3 laptops running Windows 7 SP1 with AIS. I have the "Secure DNS cannot run on this network" on all 3 machines. I've tried the Avast repair via Windows Control Panel, to no avail. This started a few days ago.
-
I.m using Windows 7 home premium SP 1. My problem started 2015.10.03. Eveything is updated. A member of the Avast team posted that they have had some problem with their secure server but that problem was now solved ? Everything shows green in the Avast UI All shields are up and everything is updated. But still that message apears about the secure DNS server. I was hoping for an answer from the person from the Avast team but still nothing. I´ve tried all the so called solutions, but they made no difference. So hopefully the rest of Avast is working. I have run all the different security checks in Avast pro antivirus and nothing seems wrong. But I just wont to get rid of that message that keeps me wonder about the safety.
exactly the same for me. I tried to submit a ticket, but that Avast website has connectivity issues! good grief ...maybe they're busy fixing this and that's why they don't have time to respond in the Forum ;)
-
Ho una piccola rete domestica con due pc identici, entrambi con win 10 e protetti con Premier. In un dei pc tutto è ok, nell'altro appare la scritta: "Non è possibile eseguire Protezione DNS su questa rete". Ho provato a reinstallare Premier, ma senza successo. Avete notizie?
-
Ho una piccola rete domestica con due pc identici, entrambi con win 10 e protetti con Premier. In un dei pc tutto è ok, nell'altro appare la scritta: "Non è possibile eseguire Protezione DNS su questa rete". Ho provato a reinstallare Premier, ma senza successo. Avete notizie?
Please post English here, else use the forum section for your language.
-> https://forum.avast.com/index.php?board=21.0
-
wanted to let you all know that I have submitted a Support Ticket on this issue. I've not yet received any email confirmation but hopefully we'll get some answers. If so, I'll let you know.
-
Great! Mine is up and running again fine. It has obviously been fixed, thank you :)
-
It is fixed :)
-
it is also fixed.
-
it is also fixed.
Also for what ???
-
Great! Mine is up and running again fine. It has obviously been fixed, thank you :)
hmm, mine is not. but I'll reboot to see if it might be - fingers crossed that all is now well
-
Great! Mine is up and running again fine. It has obviously been fixed, thank you :)
hmm, mine is not. but I'll reboot to see if it might be - fingers crossed that all is now well
restart did the trick. Hooray! Thanks Avast! Tech Team!!
-
This resolved itself with a restart after a VPS update yesterday, on all 3 laptops. All 3 machines are shut down nightly.
-
Yup, works for me now also.
A reason and some info about why we all had the problem would be nice tho...
-
Yup, works for me now also.
A reason and some info about why we all had the problem would be nice tho...
Server side issues.
-
As from today the message about secure DNS server is gone. Without doing nothing on my side. So evrything is back to normal again ?
-
As from today the message about secure DNS server is gone. Without doing nothing on my side. So evrything is back to normal again ?
Yes, the problem was resolved.