Hosts important must see

NOTE #1:

In Windows 2000/XP/2003/Vista/2008 DNS Client service (if enabled) loads the entire contents of the existing HOSTS file (if any) into the DNS cache, which may slow down the computer, especially if using a (very) large HOSTS file.
You have 2 choices here:

  1. One way is to stop and/or disable DNS Client service: Start button -> Run... box -> type services.msc -> click OK or press Enter -> open DNS Client -> General tab -> set to Manual (if needed) or Disabled (if not needed) -> Stop (if running) -> click OK or press Enter -> reboot.
    To set DNS Client to Manual (if needed), run these 2 commands from a DOS console or a batch file:

    SC CONFIG DNSCache START= demand
    and:
    SC STOP DNSCache
    or:
    NET STOP DNSCache

    To set DNS Client to Disabled (if not needed), run these 2 commands from a DOS console or a batch file:

    SC CONFIG DNSCache START= disabled
    and:
    SC STOP DNSCache
    or:
    NET STOP DNSCache

    To determine if you need to have DNS Client service enabled: Start button -> Run... box -> type services.msc -> click OK or press Enter -> open DNS Client -> Status column -> should state Started (if needed) or should be empty (if not needed).
    More info:

    CAUTION:
    Stop/Disable DNS Client service ONLY if NOT connected to/part of a network/domain.
    If connected to/part of a network/domain, DNS Client service may be necessary for proper operation.
    More info:

  2. The other way is to force the DNS cache (if DNS Client service is active) to read the entire list of servers from your HOSTS file by running this command from a DOS console or a batch file:

    IPCONFIG /flushdns

    More info @ MSKB.

NOTE #2:

In case you are running ANY network/server on your local computer, you •MUST• edit your HOSTS file using Notepad or better text/ASCII editor/viewer and change ALL 127.0.0.1 entries (except the 127.0.0.1 localhost line) to read 0 (or 0.0.0.0).
Restart or log back into your network/server when done.
Otherwise you might get a huge number of login popup prompts while trying to access the local server/network, because localhost is always located at the 127.0.0.1 IP address.

NOTE #3:

In case you cannot access an internet site/server, and if your web browser/e-mail client/ftp client/network tool returns a message/page/screen similar to (depending on the web browser/client/tool used):

this may be due to a 0 (0.0.0.0 abbreviated) or 127.0.0.1 entry into your HOSTS file associated with the internet site/server you are trying to access.
To (re)enable that particular internet site/server, just delete/remove or comment/remark that entire line: edit your HOSTS file using Notepad or better text/ASCII editor/viewer and place a # symbol in front of that line.
Then restart your web browser/e-mail client/ftp client/network tool and access that same internet site/server again.

NOTE #4:

In case Internet Explorer web browser does NOT allow you to save a web page, and you get this error message (or similar):

"Error Saving Web Page
This Web page could not be saved"

this may be due to 1 or more 0 (0.0.0.0 abbreviated) or 127.0.0.1 entry/entries into your HOSTS file associated with 1 or more of the internet site(s)/server(s) you are trying to save that web page from.
To temporarily access that/those particular internet site(s)/server(s) and be able to save it/them properly as web page:

  1. Copy & paste that URL name from the Internet Explorer URL address box: highlight the entire URL line -> right-click on it -> select Copy.
  2. Close/exit that particular Internet Explorer instance.
  3. Rename to any other name or move to any other valid location your HOSTS file.
  4. Restart Internet Explorer.
  5. Highlight the entire URL address box -> right-click on it -> select Paste -> press Enter.
  6. Now save your web page again.
  7. Close/exit that particular Internet Explorer instance.
  8. Rename BACK to the original name or move BACK to the original location your HOSTS file.
  9. Restart Internet Explorer.
This is because webmasters sometimes include server-side code to access more than 1 web site/server from within the same web page.

FYI:
If you don't understand some of these abbreviations/acronyms/terms, please look them up.