Why does 'localhost' in web references cause SocketExceptions?

Question

I have two .net web services deployed to the same IIS server using SSL, one that references the other.

If I set that web reference to 'localhost', some calls fail with this exception:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it

If I set it to the actual machine name, it works.

Why?

Answer 1

I suspect you'll find that IIS is configured to listen for requests on the "real" network interface but not on the loopback adapter.

You should be able to see this with a plain browser - try going to https://localhost on the box and see what happens.

Answer 2

The 127.0.0.1 possibly can resolve the problem. Why? I dont know- get from the experiments.

Answer 3

Hi I have the same problem, how did you resolve it. Please help me if you can because i am stuck