Why does 'localhost' in web references cause SocketExceptions?
- by Sam
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?