Problem with the hosts file in Windows XP

Question

I have a computer with Windows XP SP2 with a weird problem. The hosts file doesn't work. No matter what I do, adding or removing entries in the file doesn't make any difference, pinging the added names times out. I tried flushing the DNS cache (using ipconfig /flushdns) but that didn't work, I even tried to restart the DNS client service but that made no difference too.

Removing entries also has no effect, I ping the names and I get a reply.

Help!!!

Edit: Thanks for your answer guys, but the problem is more complicated than this. It seems I'll have to reinstall Windows.

Answer 1

Last time that happened to me, I was letting notepad name the file hosts.txt.

It must be named hosts - no extension. Change notepad save as to ..

Answer 2

Suggestions:

1- Make it is named "hosts." with no extension. As another commenter noted, sometimes editors will try and impose their default extensions.

2- Make sure you are using the file in the correct location. On my XP box it is C:\WINDOWS\system32\drivers\etc

3- Make sure that the entries you are trying to make are properly formatted. In particular, do not prefix the line with a #; that indicates a comment/remark.

Are you sure about the re-install? I am all for it, I do it once or twice a year to clean the fluff, but what makes you think it will solve the issue with (basically) name resolution?

Good luck

Answer 3

please take this Link as a Reference how to handle and setup your hostfile.

http://www.mvps.org/winhelp2002/hostsfaq.htm

Furthermore, take a look into your Windows Event Log if any error is thrown.

Good Luck,
rAyt

Answer 4

If you entered the default IP for address, 127.0.0.1, you always get a reply for ping, because you are pinging yourself. Instead do a nslookup and see if proper IP is being returned. The idea of hosts is not to block traffic, but to redirect addresses.

Answer 5

The hosts file is for resolving the name to ip address. If your problem is a lack of reply (and the address is correct) then that is another problem.

Have you verified your network is working by pinging the ip addresses instead of the names?

Use the -a option on the ping command 'ping -a ipaddress' to help you figure out the name resolution.

If the name/address resolution is working, use the tracert command 'tracert myhost' to help you figure out where your packets are getting lost.

Answer 6

Make sure you don't have any trailing space after the hostname or it won't resolve either. If you have an entry like '10.10.10.10 yourhost ' and you try to 'ping yourhost' you'll get an unkown host.

BR, Mike

Answer 7

Delete the "etc" folder and replace it("etc") from another user, who hots enterties are working fine.

Answer 8

I had the same problem and I saw in the Event Log an error every time I tried running a ipconfig /flushdns that said 'There was an error while attempting to read the local hosts file.' What fixed the issue for me was to delete and recreate the host file. For some reason that worked just fine.

Answer 9

Had the same issue, after a new XP baseline was installed on my computer at work. My previous hosts file was reinstalled in C:\WINDOWS\system32\drivers\etc and I was given write permission to it (so I could modify it if necessary) but I couldn't ping/RDP/ssh to any of the machines by hostname. Tried flushing DNS cache, rebooting, etc, to no avail. Solution was to save hosts to hosts.bak, recreate hosts with default permissions (from parent folder) and paste in the old data. I could then RDP/ping by hostname, and Windoze Admins then able to give me write permission, and it still worked.

Answer 10

Solved here...

I had the issue when I had IIS installed. There is a separate host file called:

hosts.ics

Append any changes in this file instead of hosts