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.

I am unable to connect to localhost and http:// 127.0.0.1 on one of my machines. However http://machinename works.

This results in the Windows Token Application being not able to issue tokens, because it can't connect.

This is showing up in the event log:

Request for security token failed with exception: 
System.ServiceModel.EndpointNotFoundException: Could not connect to 
http:// localhost : 32843/SecurityTokenServiceApplication/securitytoken.svc/actas. 
TCP error code 10061: No connection could be made because the target machine actively 
refused it 127.0.0.1:32843

I am able to ping to localhost:

Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

likewise for 127.0.0.1

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

The hosts file is unaltered and has no active entry in it.

After issuing the netstat -ao | findstr LISTENING command in Powershell I found these 2 entries:

TCP 172.16.2.187:32843 machine:0 LISTENING 4 TCP 172.16.2.187:32844 machine:0 LISTENING 4

which look ok and indicate that the service is up and running. In addition, every Application pool is up and the websites are running and also accessible from the outside (read our LAN).

If you need additional information please ask for them in the comments and I will add them to this post.

Please help me in finding the missconfiguration. Kind regards.

share|improve this question
    
on which port your iis daemon is running? 32843 is this port is allowed on your server firewall? –  Abhishek Anand Amralkar Nov 29 '13 at 9:28
    
The server firewall is deactivated; but the appropriate rules are specified. But this is not about the ports, but the fact that localhost does not work - on any port –  Serv Nov 29 '13 at 9:29
    
Does the machine have multiple IP adresses? I had the problem and had to set localhost to point to a specific IP address in the hosts file to get it to work. –  UnusualMutant Jan 31 '14 at 10:06

1 Answer 1

TCP 172.16.2.187:32843 machine:0 LISTENING 4 TCP 172.16.2.187:32844 machine:0 LISTENING 4

Your service is bound only on 172.16.2.187 and not to the loopback addresses (127.0.0.1, ::1:). You need to reconfigure IIS to listen on the loopback address of your choice, either IPv4 or IPv6, or listen on all available addresses (0.0.0.0) as appropriate.

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.