Cannot reach about 6 of 100 websites – ESET Live Grid Error

Topic

New Reply

Please move this if a better forum is appropriate.

Just sent this to Eset:

Eset reports: “The Eset Live Grid Servers cannot be reached” as of this morning. Has worked on this computer for years! I have changed nothing.

I cannot get to about 6 web sites I visit daily on this computer. My Mac, without Eset get there on the same wi-fi easily.

I tried disabling Eset for 10 minutes and still cannot get to those sites. “Server not found”.

What can I do?”

So, my iPhone and Mac all on the same WiFi have no issue. This PC is the only one with ESET and this error is new as I woke this morning. Their forums are not much help.

Funny I can get almost everywhere but about 6 sites (among the maybe 120 I tried) and only on this computer. Too coincidental the Eset error message. In the past, rebooting always restored in the maybe 3 times this has happened over 15 years of Eset.

I’d like:

A solution quick and easy :), Or…

Thoughts about stripping Eset Nod32 AV and relying only on Defender

Has anyone ever totally removed ESET if this persists? I hear it is not easy! And then what would need to be done to make Defender the only AV?

Really appreciate thoughts. Concerned on this one.

~Bob

Reply | Quote

Replies

Eset error not showing right now but still website issues. Could be error suppressed. Could need a reboot. Watching all closely and trying to correlate changes. I suspect it will only be a few minutes until the Eset erro again. But if that is not the issue, then truly baffled.

Back with upodates if I have them….

Reply | Quote

Definitely not browser related. Definitely not Wi-Fi related as site open on other computer, BUT they open more slowly than most other sites. Hmmm. Gonn reboot. Again…

Reply | Quote

Eset Live Grid error back. I am hoping this is the problem for websites and I am not having two issues coincidently. Gonna do lunch, then back to Google others experiences and see what to do.

Reply | Quote

That could be a DNS error on your machine as you can’t reach Eset or other sites.

Can you ping the sites you can’t reach?
Open a CMD prompt – Win R, cmd
Type: ping http://www.askwoody.com
Or whatever the name of the site is.

cheers, Paul

Reply | Quote

Live Grid error gone – again.

Will try some pinging. Good idea, Paul. Right back.

 

Reply | Quote

Eset grid error back again.

Pinged askwoody  and google with success. Tried two of the suspect sites and both cme back “could not find host”.

Just a reminder, this all worked yesterday. So would be surprised if DNS as that has not changed in forever. But, let’s try.

I only connect wirelessly on this computer and to my in house Verizon router. Mac and iPhone have no issue. So where should I check for DNS on this PC and what to try to change to? I would suspect I am on 8.8.8.8 as that had always been my usual.

Thanks!

Reply | Quote

So, under the Network Connections, WiFi, IPV4, the DNS is set to obtain automatically.

Reply | Quote

OK. I am starting to believe that the Eset Live Grid is a symptom, not the cause. Just found another site with the issue.

So what would cause only SOME sites not to be found while MANY others have no issue? And only on this computer while others with same WiFi have no issue. And with DNS set to automatic?

Must get something to eat. Back soon.

Reply | Quote

Type: ipconfig /all
This will list the DNS used by Windows.

Check your browser DNS (under Privacy / Security). Does it use “secure DNS”?
If so you may be bypassing Windows DNS. You can try changing this.

cheers, Paul

Reply | Quote

Eset error gone again. Still site issues.

Recall it is more than one browser, Paul. Firefox my daily. I do not see anything for Secure DNS or DNS settings at all in Firefox. And they would not have changed since yesterday.

Reply | Quote

Checked both Edge and Firefox. Same sites still no response. Almosyt any other site just fine in both. And fine on the Mac.

Eset Live Grid error still down, but trying to update Eset is taking forwever. Has not faile,d but usally checks in seconds, not minutes like now.

Pings still no response, but foine to Woody, Google, etc.

About to check Events for errors.

Reply | Quote

In Firefox.
Settings > Privacy and Security.
Scroll down to “DNS over HTTP”.
Choose “Increased Protection” to test.

cheers, Paul

Reply | Quote

No change. Even after closing and reopening Firefox. Still these half dozen sites. both browsers, only this computer on same WiFi as 6 others

Weird, eh?

So my take at this moment:

Eset is a symptom, not cause. Right now still no error.

Not the router.

Not DNS.

Something on THIS computer that changed in the last 24 hours. Al I see was an edge update ovwernight.

Only SOME sites have the issue. A few others slow, but function. Yet another few others open but do not populate some of the page features such as videos.

Willing to try anything.

Thanks!

 

Got a clue in next post:

Reply | Quote

OK, this seems to correlate to occurrences of the issues. Cannot fathom why. Have had COMMON Bonjour errors for years while using iTunes on this computer, but touched nothing Apple today. But, does this help at all?

Log Name: Application
Source: Bonjour Service
Date: 1/25/2025 1:51:49 PM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Winten-P51S
Description:
mDNSCoreReceiveResponse: Received from 10.0.0.11:5353 16 Winten-P51S.local. AAAA FD12:768D:C8C6:0001:5404:5C28:9920:C251
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Bonjour Service” />
<EventID Qualifiers=”0″>100</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2025-01-25T18:51:49.7529261Z” />
<EventRecordID>753530</EventRecordID>
<Correlation />
<Execution ProcessID=”0″ ThreadID=”0″ />
<Channel>Application</Channel>
<Computer>Winten-P51S</Computer>
<Security />
</System>
<EventData>
<Data>mDNSCoreReceiveResponse: Received from 10.0.0.11:5353 16 Winten-P51S.local. AAAA FD12:768D:C8C6:0001:5404:5C28:9920:C251</Data>
</EventData>
</Event>

Reply | Quote

I think those errors were only at reboot times. Likely not it. at all.

Back to other hypothoses.

 

Reply | Quote

Exactly what error do you get in the browser on sites you can’t access?

cheers, Paul

Reply | Quote

<h1 class=”title-text” data-l10n-id=”netTimeout-title”>The connection has timed out</h1>

<p id=”errorShortDesc” data-l10n-args=”{"errorMessage":"","hostname":"www.sunshinestatervs.com"}” data-l10n-id=”cert-error-ssl-connection-error”>An error occurred during a connection to http://www.sunshinestatervs.com.</p&gt;
<p id=”errorShortDesc2″></p>

<li data-l10n-id=”neterror-load-error-try-again”>The site could be temporarily unavailable or too busy. Try again in a few moments.
<li data-l10n-id=”neterror-load-error-connection”>If you are unable to load any pages, check your computer’s network connection.
<li data-l10n-id=”neterror-load-error-firewall”>If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

Now, I missed the ipconfig /all message. Good idea. I use these things so rarely I forget them: here is the pertinent: Not understanding why it shows three of these wirele???Host Name . . . . . . . . . . . . : Winten-P51S
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : F8-34-41-63-5D-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : FA-34-41-63-5D-CB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265
Physical Address. . . . . . . . . : E2-2E-A9-46-29-56
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd12:768d:c8c6:1:5404:5c28:9920:c251(Preferred)
Temporary IPv6 Address. . . . . . : fd12:768d:c8c6:1:25a9:f7f3:967a:da4d(Preferred)
Link-local IPv6 Address . . . . . : fe80::d639:1394:da21:8be2%7(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, January 25, 2025 1:50:17 PM
Lease Expires . . . . . . . . . . : Sunday, January 26, 2025 1:51:27 PM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 132263593
DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-E2-2E-A9-46-29-56
DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888
2001:4860:4860::8844
10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Going to try to flush DNS cace  and see if Eset updates now that has not has a Live Grid Error in a bit.

Back….

Reply | Quote

Timed out is not a DNS error. It is a routing / internet issue.
As it’s only that machine I would reset the IP stack.

cheers, Paul

Reply | Quote

Its fixed, and don’t ask me why!!

Unplugged the MESH router for a moment ro two. Replugged. all back.

Makes no sense to me why so selective.

Reply | Quote

Each machine has a unique address. Your routers had that address confused and now they remember what to do.

cheers, Paul

1 user thanked author for this post.

TechTango

Reply | Quote

Thanks Paul. Sincerely appreciate the help.

I now have a sign above my monitor saying “Unplug the Router”.

~Bob

Reply | Quote