Windows 2000 - Hosts File Conflict

Numerous Windows 2000 users have reported and attempted to resolve a consistent problem with large host files in any Windows 2000 environment.

This provides a solution for the single PC setting.  For those who are networked, even with one other PC in a LAN, and especially those LANs who use a dial-up connection to the internet, this offers no solution, although it may clarify the problem and offer hints toward one.

The problem is dual.  When a large hosts file is established on a Win2k system, there is a problem of a dramatic slowdown of Win2K and the inability to obtain an ISP verification and registration after a dial-up connection is made.  Even if a hosts file has only four URL redirectives, ISP verification can be interrupted.

The solution is simple:

          1.  Close the modem (if it's connected).

          2.  Stop and Disable two Windows Services - DHCP Client and DNS Server.1

                    Go to:     Start => Programs => Admin Tools => Services,

                    or Settings => Control Panel =>Admin Tools => Services.

                     Right-click => Properties for each of these services.

                     Service Status:  Stop button.

                    Startup type:  Disabled.

                    Apply button, then OK button.

          3.  Restore your personal hosts file (by renaming active and inactive files).

          4.  Reboot.

When these services are disabled, dial-up connections and browsing will be much faster than ever!  These services are not helpful if you are not networked.  Microsoft tends to include many features which are installed and enabled by default, although they may be unutilized and slow down the computer.  They get less technical support calls if they keep things simple and uniform.

The DNS Server determines and caches Domain Name System (DNS) names for the network. The DHCP Client (for Dynamic Host Control Protocol) automatically assigns IP addresses and domain names to the computers on the network -- desirable features only if you have one.

1. Quite a few people have reported that there is no Win2k service called DNS Server. They report that it should be the DNS Client service that should be disabled. I have verified on my Win2k dialup system that I do not have a DNS Server service. I have disabled DNS Client without any problems. Please be aware that this procedure may not work for everyone, some setups may require DNS Client. If you have problems re-enable the DNS Client service.

The above statement makes the next one a little confusing. All I can figure is this must be one of the situations where the users system requires the DNS Client service to function. Anyway, I'm putting this information here for everyone so you can decide for yourselves to use it or not.

Just to clarify a little, make sure that you are disabling the DNS Server and not the DNS Client. If the DNS Client is disabled the OS will not be able to resolve IP addresses. This suggestion was submitted by LA. Also it has been reported that if you are a cable modem user, specifically Road Runner, then disabling DHCP Client is not necessary.