NT/IIS 4.O 127.0.01 problems

Make sure you can goto a dos prompt and ping the localhost by typing
ping localhost
the system should come back with 127.0.0.1 if not the you may need to add it to your hosts file located in the following location.
c:\winnt\system32\drivers\etc\hosts
and besure that it is defined in this file.
localhost 127.0.0.1

Let me know if you need more help or advice.

If this is from the browser then check if you have configured a proxy. Exclude the local ip addresses from going through the proxy.

How are you trying to restore the web administration application?
The safest way is do that from the Inetsetup.exe program (The IIS Service Installation).
You can access the web based administration page by going to:
http://localhost/iisadmin/iis.asp

I can't browse to http://localhost/iisadmin/iis.asp due to the error I stated. Actually, I've fixed the problem by setting the Administrator Web Site to publish c:\inetpub\wwwroot and set the IP to 127.0.0.1. I don't understand why I have to do this though.

This is a duplicate.

MFK, there is no proxy.
WayneB, I can ping localhost.

This maybe a bug in Microsoft's web server, if you can ping localhost is a valid address that should work if you browse to it. I tryed to look it up in the Ms knowledge base and found no reference to this problem, but it should work and it does not.

Does your IIS use all avaliable IP addresses? If you configure one to use only specified IP it not binded to localhost address.

vvk: No, I've allocated about 10 IP's to the Server, of which only 6 are being used. Should I set the Administrator Web Site to <All Unavailable> instead of giving it an IP? What the heck does that mean anyway?

I'm only accepting this answer to get it off the question list. IIS sure does some strange things at times.