am_dew
-
Posts
40 -
Joined
-
Last visited
-
Days Won
1
Posts posted by am_dew
-
-
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.
-
23 hours ago, Marcos said:
Unfortunately the screen shot above is blurred so I can't tell if it's the same network being detected.
Try leaving only these two parameters enabled for this network identification:
@MarcosWere you ever able to determine if the same network was detected?
Thanks.
-
54 minutes ago, itman said:
Since you state this issue is intermittent in nature, another possibility is the use of APIPA address DNS server assignment.
APIPA IPv4 DNS server addresses start with 169.xxx.xxx.xxx and are used when DHCP initialization processing cannot establish a valid IPv4 DNS server connection
Unfortunately Eset network processing doesn't handle this situation at all and will indeed try to great a new network connection when it occurs.
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) ?
-
2 minutes ago, itman said:
If the IPv4 DNS server addresses shown in this screen shot; i.e. 75.75.75.75 and 75.75.76.76, are your actual router assigned IP addresses, I question their validity. IPv4 DNS server addresses on a device almost always are within the assigned local subnet range; 192.xxx.xxx.xxxx or 10.xxx.xxx.xxx.
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.
-
11 minutes ago, itman said:
I would suggest you open a command prompt window and enter the following:
ipconfig /all
The output shown will give details as to DNS server, DHCP server, and gateway IP addresses in use by Win 10. Eset Network Identification parameters should match that shown in the ipconfig output in regards to the above noted IP addresses.
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.
-
12 minutes ago, itman said:
What usually causes this is the parameters assigned to the Eset network profile for the device are too restrictive. Refer the below screen shot.
The clause to note is:
What this means is if your device and local network parameters do not match all the data shown in the Network Identification section, Eset will not recognize the existing network adapter connection and attempt to create a new one. You might have to experiment with different settings in this section; notably DNS and DHCP server IP addresses.
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.
-
3 minutes ago, am_dew said:
Those two parameters are, and have always been, enabled whenever I checked. Here is an unblurred screen shot.
-
4 minutes ago, Marcos said:
Unfortunately the screen shot above is blurred so I can't tell if it's the same network being detected.
Try leaving only these two parameters enabled for this network identification:
Those two parameters are, and have always been, enabled whenever I checked.
-
1 minute ago, itman said:
Something is not right here.
When Eset established the initial network adapter profile for this device, assumed it was the trusted Home/Office profile. This would have set the the Trusted zone for example to 192.168.0.0/24. In other words, all devices connected to the local subnet assigned by your router.
How are you doing file sharing with the other devices on the network? Via recommended Win 10 folder sharing method?
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?
-
16 minutes ago, am_dew said:
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?
Log files attached.
-
8 hours ago, Marcos said:
The dialog pops up whenever a new network is detected. If you don't roam between new networks ESET should remember your choice for the given network. If you want to treat any new network as public automatically, you can configured it here:
You can provide logs collected with ESET Log Collector so that I can check if various networks were actually detected and your choice was remembered.
Note that public networks have certain services blocked, such as file sharing.
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!
-
2 hours ago, itman said:
Eset's .dll for Win 10 AMSI is not properly code signed although Eset states otherwise. This is why those errors are occurring. As best as I can determine, eamsi.dll is being injected eventually into some but not all of the processes where the code integrity error occurs.
So for all practical purposes, this error can be ignored and is not noticeably affecting performance?
-
21 minutes ago, itman said:
Verify that the code integrity log entries are for ecmds.exe and not eamsi.dll.
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?
-
-
6 minutes ago, itman said:
Although not directly related to this Eset Chromecast issue, it is imperative that one validate that ports 8008, 8009, and 8443 are not open on the WAN side of the router. Before you ignore this, read this Sophos article: https://nakedsecurity.sophos.com/2019/01/04/dont-fall-victim-to-the-chromecast-hackers-heres-what-to-do/
Can this thing we call technology get any more complicated? I really feel for the non-IT types.
-
50 minutes ago, itman said:
Check this out: https://support.google.com/chromecast/answer/3249268?hl=en . Run the automated troubleshooter first.
Thanks, I tried all that including a factory reset of the Chromecast dongle without success. I give up.
-
4 minutes ago, lamar said:
@am_dew Did you try to connect with another NIC? If it is a laptop, disable WiFi and try connecting wired. If your rig is not equipped with a wired NIC, a cheap USB2/100BaseT will be worth a try. Also, you can try to set up a VM on that PC. Do not forget to configure the VM's NIC from NAT to Bridged. Install a fresh Windows along with a single Chrome on the VM.
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.
-
30 minutes ago, itman said:
I am far from an expert when it comes to IoT connectivity.
But based on this article: https://blog.bestbuy.ca/tv-audio/tv-home-theatre-tv-audio/how-to-connect-chromecast-chromecast-audio-to-your-av-receiver , connecting the Chromecast dongle to an AV receiver only allows for output from that dongle to anything directly connected to the AV receiver. That usually is a TV, X-Box, etc..
It appears latter version Onkyo receivers haves Chromecast built-in but that is only for audio streaming.
In other words in this configuration, I see no way how your PC not physically connected to the AV receiver could communicate with a Chromecast dongle attached to the AV receiver.
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
-
15 minutes ago, itman said:
Onkyo equipment is notoriously temperamental.
This also might be routing issue. PC that can't connect to Chromecast device can't "see" the dongle since it is connected to the AV receiver.
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.
-
Just now, itman said:
Since it appears you are using Chromecast on multiple network devices, on which device is the dongle attached to?
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.
-
Just now, itman said:
Did Chromecast work properly on this device prior to ver. 12.2.23?
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.
Exporting settings
in ESET Internet Security & ESET Smart Security Premium
Posted
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!