HOSTS file slowing down connecting times?

[Peter]

Hi guys...

I just discovered something really WEIRD today. As I was
mucking around in my C:\WIN2K\SYSTEM32\DRIVERS\ETC
directory, I clicked on the HOSTS file, intending to open
it in notepad and have a look. The size of the file is 300K
(lots of ad sites blocked heheheh!).

The strange thing is that, the whole computer seemed to
slow and felt sluggish while I was trying to open this.

So anyway, I closed the file once it had opened, and killed
the entire file. Then I created a new one with only 1 entry
- 127.0.0.1 as localhost.

Then BAM! The problem which I've been having for a few
weeks of dialup connections seems to take very long to
connect went away. Suddenly I get instant connects again!

I tested it again by copying back a backup HOSTS file,
which was the 300K one, as "HOSTS". Again, the whole system
slowed even when I just clicked ONCE to highlight it.
Re-dialling to my ISP again slowed, ie takes a minute to
connect instead of the near-instant connects I get with the
<1K file with only 1 entry.

Now, I am wondering, why does the size of the HOSTS file
affect the DUN connecting times? For that matter, why does
the size of the HOSTS file affect the whole computer in the
first place?

 

[me]

DUH....maybe because it has to check the whole file before it can load
anything?!
It even has to check the file before connecting because your ISP maybe
re-directed. It has no way to know what you want it to do unless you
tell it and by having the file you are telling it to check the file
BEFORE doing anything!

Hi guys...

I just discovered something really WEIRD today. As I was
mucking around in my C:\WIN2K\SYSTEM32\DRIVERS\ETC
directory, I clicked on the HOSTS file, intending to open
it in notepad and have a look. The size of the file is 300K
(lots of ad sites blocked heheheh!).

The strange thing is that, the whole computer seemed to
slow and felt sluggish while I was trying to open this.

So anyway, I closed the file once it had opened, and killed
the entire file. Then I created a new one with only 1 entry
- 127.0.0.1 as localhost.

Then BAM! The problem which I've been having for a few
weeks of dialup connections seems to take very long to
connect went away. Suddenly I get instant connects again!

I tested it again by copying back a backup HOSTS file,
which was the 300K one, as "HOSTS". Again, the whole system
slowed even when I just clicked ONCE to highlight it.
Re-dialling to my ISP again slowed, ie takes a minute to
connect instead of the near-instant connects I get with the
<1K file with only 1 entry.

Now, I am wondering, why does the size of the HOSTS file
affect the DUN connecting times? For that matter, why does
the size of the HOSTS file affect the whole computer in the
first place?

-- Have you checked your Smoke Detector...LATELY?

 

[Peter]

DUH....maybe because it has to check the whole file before
it can load

anything?!

Even if I'm just using Windows Explorer to look at the
file? And not even connected to any sort of network?

Okay, that's news to me. I've always thought whenever a
name resolution is required, the presence of the HOSTS file
tells it to look there first, and clicking around inside
your Windows Explorer does not qualify a "name resolution
request".

Well, ya learn something new everyday. Thanks.