Jump to content

limited Direct Cloud connectivity issue


Super_Spartan

Recommended Posts

Running NOD32 Antivirus 17.0.15.0 , I am getting this popup notification from time to time randomly:

limited Direct Cloud connectivity issue

ScreenShot80.png.ee15df9ab4b34625b2b3bca22ed51398.png

I have the ESET GUI and ekrn.exe rule set to allow in my Windows Firewall settings.

I am running the latest build of Windows 11 23H2

After getting that popup, I see everything looks ok in the main UI, no notifications

 

Is this like a temporary glitch?

Edited by Super_Spartan
Link to comment
Share on other sites

  • Administrators

Please enable advanced direct cloud logging under Tools -> Diagnostics and keep it enabled while troubleshooting the issue. When the error occurs, collect logs with ESET Log Collector and supply the generated archive for perusal.

Link to comment
Share on other sites

1 hour ago, Marcos said:

Please enable advanced direct cloud logging under Tools -> Diagnostics and keep it enabled while troubleshooting the issue. When the error occurs, collect logs with ESET Log Collector and supply the generated archive for perusal.

Here it is

ScreenShot83.png.1989a9913022f4a00c8c71c6d6b3038d.png

 

eav_logs.zip

Link to comment
Share on other sites

  • Administrators

Looks like all DNS servers were unreachable:

24.11.2023 15:26 Failed connect to 10.128.172.1@53 (UDP)
24.11.2023 15:26 Failed connect to 192.168.50.1@53 (UDP)
24.11.2023 15:26 ERROR [RESOLV] <dns_resolver>: Question [name: avcloud.e5.sk, type: A] Resolve failed

Link to comment
Share on other sites

27 minutes ago, Marcos said:

Looks like all DNS servers were unreachable:

24.11.2023 15:26 Failed connect to 10.128.172.1@53 (UDP)
24.11.2023 15:26 Failed connect to 192.168.50.1@53 (UDP)
24.11.2023 15:26 ERROR [RESOLV] <dns_resolver>: Question [name: avcloud.e5.sk, type: A] Resolve failed

I notice every time I connect to my VPN (I use hide.me) this is happening after a few minutes. This never happened in the past I've been using the same VPN and NOD32 for years

 

just pinged: avcloud.e5.sk

ScreenShot84.png.79a0b51512f04906d80a5f47721468b6.png

Edited by Super_Spartan
Link to comment
Share on other sites

  • Administrators

Could you please reproduce the issue by connecting to VPN and let Wireshark log the network communication? Also enable direct advanced logging as we'll need to have both logs aligned. When done, please supply the Wireshark log and the content of the "C:\ProgramData\ESET\ESET Security\Diagnostics" folder.

Link to comment
Share on other sites

37 minutes ago, Marcos said:

Could you please reproduce the issue by connecting to VPN and let Wireshark log the network communication? Also enable direct advanced logging as we'll need to have both logs aligned. When done, please supply the Wireshark log and the content of the "C:\ProgramData\ESET\ESET Security\Diagnostics" folder.

so I installed Wireshark then rebooted then connected to the VPN, for about 20 mins, I didn't get that error from NOD32, then the moment I opened NOD32 and clicked on update, the issue appeared, I then went to Wireshark and stopped the packet capturing but got this message:

ScreenShot85.png.dcc2f68253667c6b50c5924cf66cb144.png

 

I didn't see it logging anything.

I will format my laptop later as I need a fresh start anyway, hopefully this won't come back again and since I'm the only one who mentioned this issue, maybe it is something with my system

Link to comment
Share on other sites

  • Administrators

Are you really connected via wi-fi which was selected on the initial adapter selection screen? There you can see also a graph with network activity next to each adapter which helps you choose the active one.

Alternatively you can temporarily  install ESET Internet Security or ESET Smart Security Premium and activate it with a trial license. These contain the network protection feature and can log network communication to pcap files which can be activated by enabling advanced network protection logging under Tools -> Diagnostics in the advanced setup.

P_ESSW-17564

Link to comment
Share on other sites

I am wondering if this issue is due to Eset reverting to Google DNS 8.8.8.8 server when it has cloud connectivity issues? This might not play nicely with the VPN being used.

Edited by itman
Link to comment
Share on other sites

3 hours ago, itman said:

I am wondering if this issue is due to Eset reverting to Google DNS 8.8.8.8 server when it has cloud connectivity issues? This might not play nicely with the VPN being used/

I've added ESET GUI and ekrn.exe to the exclusions in my VPN so they don't use the VPN when I connect to it because that's what's triggering this error is when I connect to the VPN, been 15 mins and so far I didn't get that message. Will keep monitoring this and report back.

Edited by Super_Spartan
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...