Jump to content

itman

Most Valued Members
  • Content Count

    8,189
  • Joined

  • Last visited

  • Days Won

    198

Everything posted by itman

  1. Elaborating on this attack, the details are as follows. The IOBit forum website was compromised by an attacker who gained admin access to the site. This allowed him to harvest e-mail addresses of forum users and plant a malicious download from the forum web site. The attacker then sent e-mails to IOBit forum users which stated they were the winners of a free one year license to an IOBit security product. At this point note that the e-mail would appear legit since the sender's address was legit. The following are excerpts from the bleepingcomputer.com article. The ransomware i
  2. The main thing to know about this attack was Windows Defender was bypassed since the malware created exclusions in WD to allow its malicious .dll to run undetected. Kapersky also didn't stop files being encrypted by the ransomware portion of the attack. Per a malwaretips.com poster: Waiting until someone does a detailed analysis on this puppy.
  3. A bit difficult to understand what you posted. Eset has three retail products with a firewall: 1. Internet Security 2. Smart Security Premium. 3. A legacy product called Smart Security. This has been superseded by Internet Security. Which of the above did you have installed previously? Which of the above did you recently install? Did you uninstall what you had installed previously prior to performing the new install?
  4. You can make an inquiry as to pricing here: https://www.eset.com/my/business/windows-security/
  5. The way to diagnose this is as follows: 1. Set Ethernet IPv4 connection back to Obtain DNS server automatically. 2. Reboot device or do via command prompt window, ipconfig /flushdns, ipconfig /release, and ipconfig /renew commands to reset IPv4 connection and acquire a new IPv4 lease. 3. Via command prompt window, enter ipconfig /all and note IPv4 DNS server assignment IP addresses. 4. Open Eset GUI and then Network protection. 5. Select Advanced. Then select Zones -> Edit. In the DNS section, do you see the same IPv4 DNS server addresses noted in the prior ip
  6. Are you referring to the Eset splash screen which just shows an image of Eset logo? If so, refer to below screen shot to disable its display at system start up time.
  7. I came across this posting in regards to connection-specific DNS suffice: https://community.linksys.com/t5/Wireless-Routers/Need-to-get-rid-of-quot-DNS-Suffix-Search-List-quot-from-ISP/td-p/1233151 It confirms: 1. It is assigned by Comcast ISP servers. 2. It is IPv6 conditioned. My best guess as to why it changes from hsd1.ca.comcast.net to hsd2.ca.comcast.net deals with IPv6 DNS server assignment. I suspect hsd1 is the primary IVv6 DNS server and hsd2 is the secondary server. I have never really seen anything like this before. When Eset detects the hsd2.ca.comcast.net
  8. FYI https://help.eset.com/protect_cloud/en-US/what_is_new.html
  9. NOD32 does not contain a firewall. Installing NOD32 would have no effect on any existing firewall you were previously using. Did you perhaps purchase and install Eset Internet Security by mistake?
  10. First, we are talking about connection-specific DNS suffice versus domain DNS suffix. Connection-specific DNS suffix is assigned via the DHCP initialization processing and really should never change. Also Eset uses connection-specific DNS suffice to actually name the network connection. I would talk to Comcast tech support as to why your connection-specific DNS suffix name is changing. Might be a problem with your ISP issued router. Or, there is a router configuration option to prevent this from happening.
  11. More info on the use of APIPA in Windows and when it is invoked is given here: https://www.lifewire.com/automatic-private-internet-protocol-addressing-816437
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. 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?
  17. Here's an article that lists ports used by Steam: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711 I don't see anything listed there that would conflict with protocol/ports used by LiveGrid.
  18. Based on what is shown here: https://support.eset.com/en/kb6209-set-up-security-tools-in-eset-smart-security-premium and here: https://support.eset.com/en/kb6266-eset-secure-data-faq , there is no way to change the password.
  19. Exactly.👍 Again, Eset created the secure all browsers mode to eliminate the complaint of the Win default browser in B&PP mode when another browser was used for daily browsing use. Personally, I believe Eset should just revert B&PP options back to the previous settings. All the new settings are just creating a lot of confusion.
  20. If you have no need for the parental control option in Eset; e.g. no children use this computer, etc., disable the option per the below screen shot. Note that this option is not enabled by default. Disabling the parental control option will eliminate the need to create any Eset web site exclusions in this regard.
  21. The answer is any web site can be compromised. This is why Eset is scanning HTTPS incoming Internet traffic.
  22. Refer to this: https://support.eset.com/en/kb6408-banking-and-payment-protection-browser-not-working . Scroll down to this section in the article:
  23. In ThreatSense parameters for Idle-Scan option, verify that the scan is set to low priority. See if this helps with the logon issues:
  24. Position your mouse pointer over "Marcos" in one of his forum replies as shown in the below screen shot. Then mouse click on "Message."
  25. I have no issues using B&PP with Firefox. What browser are you using?
×
×
  • Create New...