Okay, thanks.
Did clearing the DNS cache work? You didn't indicate if it did or not.
Can you ping easeus.com ? Go back into CMD and enter
Just in case you don't know. If it pings and yo see a server IP, (should be the one I gave you from before of: 216.92.151.227, then DNS resolution on your computer looks like it's working. But on its face now, DNS resolution doesn't appear to be working correctly. Right now I'm suspecting your anti-virus. Especially since this issue is broad in scope and affecting multiple browsers, but not other computers. So having said that. Try disabling the web access protection feature in Nod32 and then try going to Easeus again.
Web access protection | ESET NOD32 Antivirus | ESET Online Help
You'll note that web access protection stands between you and the Internet. The anti-virus software is literary a man in the middle intercepting your TLS/"SSL" connection. Sounds bad, doesn't? Well, it is. Because now the anti-virus is polling all your telemetry on which websites you visit. This is just one reason why I don't use anti-virus software anymore and chose to use as more unorthodox approach which you can read about
here. I'm probably more protected than someone running anti-virus software. I even scan the air gaped (disconnected) clone of my computer on the external hard drive for malware and nothing. And get this. Like you, I run "outdated and malware prone" Windows 7 and only have about four Windows updates for hardware and software needs! LOL!
Anyway, lets see if it's your anti-virus. It may, it may not, but it looks like a DNS resolution issue right now. You might want to investigate your hosts file as well. To do so, go to this path:
Code:
C:\Windows\System32\drivers\etc
Now temporally rename the hosts file hosts.txt so that you can read it. I just right click and open it with Notepad++. That's just a program for us nerds. LOL But it's a great text editor and text manipulator in so many ways, let me tell you.
Now that the hosts file is open, do you see
just this and nothing else added at the bottom?
Code:
## Copyright (c) 1993-2009 Microsoft Corp.
##
## This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
##
## This file contains the mappings of IP addresses to host names. Each
## entry should be kept on an individual line. The IP address should
## be placed in the first column followed by the corresponding host name.
## The IP address and the host name should be separated by at least one
## space.
##
## Additionally, comments (such as these) may be inserted on individual
## lines or following the machine name denoted by a '#' symbol.
##
## For example:
##
## 102.54.94.97 rhino.acme.com # source server
## 38.25.63.10 x.acme.com # x client host
## localhost name resolution is handled within DNS itself.
## 127.0.0.1 localhost
## ::1 localhost
If you see entries there that point to 127.00.1 after the very last # (technically anywhere) then it's blocking that domain. So as an example it may look like this:
Code:
## Copyright (c) 1993-2009 Microsoft Corp.
##
## This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
##
## This file contains the mappings of IP addresses to host names. Each
## entry should be kept on an individual line. The IP address should
## be placed in the first column followed by the corresponding host name.
## The IP address and the host name should be separated by at least one
## space.
##
## Additionally, comments (such as these) may be inserted on individual
## lines or following the machine name denoted by a '#' symbol.
##
## For example:
##
## 102.54.94.97 rhino.acme.com # source server
## 38.25.63.10 x.acme.com # x client host
## localhost name resolution is handled within DNS itself.
## 127.0.0.1 localhost
## ::1 localhost
127.0.0.1 easeus.com
127.0.0.1 some_web_site_I_want_to_block
127.0.0.1 sends to null (home) so it stops the domain to IP resolution in its tracts and you can't go there. The # before all that text just comments out the text so that it's not parsed (interpreted) by the hosts file. Kinda like the rem (remark) statement in a batch file.
Code:
@[URL="https://www.sevenforums.com/members/echo.html"]echo[/URL] off
ping sevenforums.com
rem my comment here so I know what this does.
exit
Malware can and will modify the hosts file. So once you rename the hosts file from a .txt back to to just hosts again, right click the hosts file, chose properties and mark it as read only. This will
help mitigate the hosts file from being modified by malware.
If after all this, and you still can't get to easeus.com, go into
safe mode with networking and try that way. Can you get to easeus.com? Report if you can or not. If you still can't get to easeus.com, this means you have something else deeper going on inside. Could be an
LSP, the
network stack, a DLL, all kinds of things.
- - - Updated - - -
Try completely uninstalling NOD32 as well if the above steps don't work. See what happens.
