Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Why does navigation to localhost on Windows Server 2008 R2?

Is there a way to fix this to allow localhost to properly work?

(As a random note, I have already tried setting DWORD: DisableLoopbackCheck 1 at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 with neither seeming to matter, I did restart both IIS and IIS Admin, I did not restart the server itself)

share|improve this question
    
What do you mean it does not work? t works on my stock installed iwndows servers. –  TomTom Dec 1 '11 at 17:16
    
do you have IE ESC turned on for your account? –  Top__Hat Dec 1 '11 at 17:18
    
Does not work as in, the server does not recognize localhost addresses, it will only accept machinename addresses. localhost/site 404, machinename/site all is good. –  Chris Marisic Dec 1 '11 at 17:27
    
@ChrisMarisic If you have a problem, Meta Server Fault is the place to discuss it. Not comments. –  MDMarra Dec 1 '11 at 18:42
    
IE ESC means Enhanced Security Configuration. What's IE SEC? –  TristanK Dec 3 '11 at 3:49

2 Answers 2

By default, this is not blocked. Chances are you haven't enabled the exception for IIS in Windows Firewall. To test, you can disable the firewall all together. If that works, you should re enable it and then enable just the necessary rules.


Update: Reading your comment, it seems that what I mentioned above isn't the problem. If 127.0.0.1 works in the browser and localhost does not, chances are something (someone?) borked your default HOSTS file. Make sure that 127.0.0.1 localhost is in there. There's nothing magic about the word "localhost". It's just an entry in the default HOSTS file that points to 127.0.0.1.

share|improve this answer
    
This answer is not relevant to my question, will downvote soon. –  Chris Marisic Dec 1 '11 at 17:29
    
What exactly isn't relevant? It was entirely relevant, given the scant amount of detail in your original question. I then updated it when you commented on your own question with more details. Downvotes should be for wrong or misleading answers. Not for answers that make an attempt to answer a vague/incomplete question. –  MDMarra Dec 1 '11 at 17:34
    
The firewall answer makes no sense, and your edit occurred after my initial comment. –  Chris Marisic Dec 1 '11 at 17:37
2  
Machinename/site works, localhost/site doesn't...are you only binding to a particular IP address and not listening to 0.0.0.0 or 127.*? –  Bart Silverstrim Dec 1 '11 at 17:39
1  
@ChrisMarisic It makes perfect sense. In your original question you didn't state that you could connect in any way. Logically, most people test using localhost before making DNS entries, so it's safe to assume (since you didn't say otherwise) that you couldn't connect at all. Then, when you commented that you could get there using the hostname, I edited my answer to make sure that your localhost-to-loopback mapping was happening properly, which is a valid suggestion given your problem. You might want to read How to Ask. It outlines why detailed questions are important to getting good answers. –  MDMarra Dec 1 '11 at 17:45
up vote 0 down vote accepted

Apparently there was no IIS binding for localhost, I guess Windows Server 2008 doesn't add that by default as Windows 7 does.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.