am_dew

If I export my EIS settings, then uninstall EIS for a few days, then if I re-install EIS, and then import those saved settings back into EIS, will things be exactly like they were before I uninstalled EIS? The reason I ask is because I want to test if something happening on my Windows 10 64 bit PC is being caused by EIS, but I want to make sure I can revert back to it without having to set everything back the way it was before the uninstall. Thanks!

I am also getting this notification on the West Coast USA.

Thank you for the research and your assistance. I went ahead and created a new Known Network in ESET for hsd2.ca.comcast.net with the same settings as the hsd1.ca.comcast.net network already present in ESET.

@MarcosWere you ever able to determine if the same network was detected? Thanks.

I have never seen APIPA DNS servers assigned but they could be used without my realizing it, I suppose. One thing I have noticed is that DNS suffix in 'Network Identification' is sometimes hsd2.ca.comcast.net when a net network is found. Is there any harm in disabling the DNS suffix option in 'Network Identification' or could I possibly use a wild card (eg. hsd*.ca.comcast.net) ?

Those are the DNS IPs assigned by the router to my PC. I checked another PC in the house and the values are the same.

The settings in the screenshot below match what I see in ipconfig /all output. As said above, I just recently decided to add the gateway IP address in addition to the previously populated DHCP and DNS server values to see if that helps. Time will tell I guess.

I had a feeling these settings were part of the equation. Yesterday, after the "new network" detection I added in the IP address of my gateway (which is also the same IP as my DHCP server) to see if that would help. So far, I have not been prompted by ESET for a new network but then again, those prompts seem to come at random times, sometime weeks apart.

Those two parameters are, and have always been, enabled whenever I checked.

Yes, I am sharing using standard Windows 10 folder sharing. I have tried deleting all "Known Networks" from ESET and then I get prompted with the message in my OP, to which I click "Yes". At some point later for some reason, I will get prompted again with the same message. Is there a way to force ESET to see my network as Home/Office?

Log files attached. eis_logs.zip

Thank you. Some background -- my network setup is pretty standard...an up-to-date Windows 10 Pro desktop PC in my house with a hard-wired internet connection via an ISP (Xfinity/Comcast) supplied cable modem/router. There are other PCs in the same house, on the same network, that I want to share files with, so whenever a new network was detected, I would always set it as a Trusted Zone (Home or office network). I downloaded and ran the ESET Log Collector. Is there a secure way I can share the ZIP file with you? Or is there anything in the ZIP file that might be considered unsecure?

I get periodic ESET messages saying "New network connection detected" and the message asks if I want to consider it as a trusted connection. What causes this message to appear, and is there a safe way to have ESET always consider it a trusted network based on something such as an IP address, domain, etc.? Thanks!

So for all practical purposes, this error can be ignored and is not noticeably affecting performance?

All of the log entries seem to be from eamsi.dll

To add to this thread, I noticed today in my Windows Event Viewer that I am getting code integrity errors. I am on x64 Windows 10 v1903 and ESET Internet Security 13.0.22.0. I have scanned my entire PC for malware with nothing detected. This started on Oct. 3. ESET seems to be running fine. EDIT: I just checked another PC of mine, same specs as above, and it also is showing this in the WIndows Event Viewer. Any suggestions/comments?

I think Leann is looking for a permanent solution, not a workaround or pre-release update. It has been a month and it's very easy to understand why some people are getting impatient.

Can this thing we call technology get any more complicated? I really feel for the non-IT types.

Thanks, I tried all that including a factory reset of the Chromecast dongle without success. I give up.

Thanks. Both desktop PCs are network connected via hard wire. I'm not going to spend any more time getting it to work since one PC connects to the Chromecast dongle fine as does my Android phone.

The A/V receiver (AVR) is connected to the TV via an HDMI port and supplies a video signal to the TV just like a cable box or BlueRay player.. The Chromecast dongle is a network device that communicates with a PC(s) or other compatible device, and essentially is just another input source for the AVR, just like a cable box is. The PC does not need to be connected to the AVR in any respect -- the Chromecast dongle is the "receiving device" here and is just passing the signal it gets on to the AVR. In this case, I have one PC which is unable to communicate with the Chromecast dongle, while another one is able. This exact setup has always worked until I replaced a PC...before then it worked on both PCs. Both PCs are on windows 10, same version of Windows, Chrome browser, etc. etc. PC --> Chromecast dongle --> AVR --> TV

What does not make any sense to me is why one PC in the same house, on the same network, can connect to the Chromecast without issue now that I've applied the temp fix. I've been through every network related setting on the problem PC and it all looks OK.

The Chromecast dongle I am not able to connect to with one of my PCs is attached to an Onkyo audio-video receiver. Both PCs that I am trying to connect to that Chromecast are on the same network...one PC is able to connect, the other does not. The 3rd PC I have is in a different physical location, different network, and a different Chromecast dongle...I have no issues with it after applying the temp fix.

No, I've never been able to get Chromecast to work on it (new PC as of Sept 2018). I was hoping that it was an ESET issue now that we've learned more about the issue and resolution.