Article ID: 283092
If you create a Hosts file in another folder or with a different name and you then copy or rename the file to %SystemRoot%\System32\Drivers\Etc\Hosts, you may not be able to resolve host names in the new Hosts file. If you open the new Hosts file in Notepad one time and then save it, you can then resolve the names in the new Host file.
The DNS Cache service waits for changes to the Hosts files from a FindFirstChangeNotification notification. However, Windows tries to open the Hosts file as soon as a change has been signaled.
This problem can also occur if another process has opened the Hosts file share in Exclusive mode.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
Date Time Version Size File name ----------------------------------------------------------------- 18-Jul-2001 20:55 5.0.2195.3858 355,088 advapi32.dll 18-Jul-2001 20:55 5.0.2195.3649 135,440 dnsapi.dll 18-Jul-2001 20:55 5.0.2195.3649 94,992 dnsrslvr.dll 18-Jul-2001 20:55 5.0.2195.3817 142,608 kdcsvc.dll 17-Jul-2001 20:08 5.0.2195.3872 197,392 kerberos.dll 26-Jun-2001 23:16 5.0.2195.3781 69,456 ksecdd.sys 17-Jul-2001 19:52 5.0.2195.3870 501,520 lsasrv.dll 128-bit 17-Jul-2001 19:52 5.0.2195.3870 501,520 lsasrv.dll 56-bit 17-Jul-2001 19:52 5.0.2195.3870 33,552 lsass.exe 18-Jul-2001 20:55 5.0.2195.3776 306,448 netapi32.dll 18-Jul-2001 20:55 5.0.2195.3776 357,648 netlogon.dll 18-Jul-2001 20:55 5.0.2195.3868 909,072 ntdsa.dll 18-Jul-2001 20:55 5.0.2195.3868 382,224 samsrv.dll 18-Jul-2001 20:55 5.0.2195.3781 128,784 scecli.dll 18-Jul-2001 20:55 5.0.2195.3649 299,792 scesrv.dll 18-Jul-2001 20:55 5.0.2195.3649 48,400 w32time.dll 29-May-2001 12:26 5.0.2195.3649 56,080 w32tm.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/249149/EN-US/ )Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
Article ID: 283092 - Last Review: June 19, 2014 - Revision: 4.0