Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Raptech who wrote (66249)	10/29/2009 10:15:46 AM
From: LTBH	Read Replies (1) \| Respond to of 110581

The hosts file (no extension) should be found in C:\Windows\System32\drivers\etc\ hosts ... or simply do a search. Unless you have already made entries OR you are using a site blocker which uses the hosts file ... there should only be the sample entry in this file. If you are using vista/7 you need to open the file using admin priviledges. For how to use either see the following or do a search ... will get plenty of hits. en.wikipedia.org ---------------- "The hosts file consists of lines consisting of an IP address and one or more hostnames, separated by white space. Comment lines in the hosts file start with the '#' (hash) character. Blank lines are ignored. The default hosts file contents typically includes a line for the localhost definition.[5] [edit] Other uses In its function of resolving host names, the hosts file may be used to define any domain name for use in the local system. This may be used either beneficially or maliciously for various effects. [edit] Redirecting local domains A useful and time-saving tip for website programmers, intranet developers, and IT managers is to enable non-standard TLDs on a LAN for various purposes, such as the domain LOCAL to access the company's intranet or to test websites in development. [edit] Internet resources blocking People also use Hosts files as a way to block online advertising (ads), or known malicious or criminal domains and servers which may contain spyware, adware, and other malware. They do so by adding entries for those sites that redirect their requests to another address (which is the dead-end destination). Often, the local (loopback) address 127.0.0.1 is used for such purposes, but is proved to be a poor choice because: 1. Some programs will run services on the loopback address 2. If you are running a webserver on your machine, you will receive unexpected hits from the browser which may hinder your server development and maintenance. Besides the server may react unpredictably if a different server is running on port 80. 3. Some programs which have to deal with local and remote traffic may act strange or report errors (eg ICSI Netalyzr, NoScript) when external requests are redirected to the local address 4. It tries to connect to the dead-end destination which wastes a bit of unnecessary time. A more suitable choice is to use a truly invalid address, for example 0.0.0.0 or 255.0.0.0, is invalid as a TCP endpoint. Apart from the above benefits it enjoys the speed benefits too since communication is immediately dropped for a truly invalid address: 0.0.0.0 badsite.com -------------------