WCF 10061 error. "Actively refused".

[m6s]

I created the WCF service library. The purpose of the program is to expose two functions.

While locally, on the same machine, when running the vs2010, the wcfTestClient executes and "speaks" with the services, on the remote pc, invoking wcfTestClient and the url, I get 10061 error. "Actively refused".

Url I use is : "net.tcp://172.16.1.138:8732/WCFEAFDSS/Box
or the same plus "/mex".

Following code is the xml. Which I think somewhere there lies the problem...Has anyone seen this message before?
Any ideas?

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <system.web>
    <compilation debug="true" />
  </system.web>
  <!-- When deploying the service library project, the content of the config file must be added to the host's 
  app.config file. System.Configuration does not support config files for libraries. -->
  <system.serviceModel>
    <services>
      <service name="WCFEAFDSS.BoxSrv">
        <endpoint address="net.tcp://localhost:8732/WCFEAFDSS/Box"
          binding="netTcpBinding" bindingConfiguration="" name="basic"
          contract="WCFEAFDSS.IBoxSrv">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexTcpBinding" bindingConfiguration=""
          name="mexEnding" contract="IMetadataExchange" />
        <host>
          <baseAddresses>
            <add baseAddress="net.tcp://localhost:8732/WCFEAFDSS/Box" />
          </baseAddresses>
        </host>
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="">
          <serviceMetadata httpGetEnabled="false" />
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>
</configuration>
 
 

[ZiadElmalki]

This is coming from a winsock error WSAECONNREFUSED. Meaning the remote machine did not want to talk to the client connecting to it.

No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.


Make sure all your address and port are correct. Check for firewalls and add exceptions if needed.

[m6s]

It seems so, but I don't have either firewall or proxy in the middle...

[Plater]

Is your service configured to allow outside connections? I think be default they are NOT

[m6s]

Plater what would be a diagram or a flow to check this? Perhaps a url link in msdn?
I found out, that services on my pc, have some names like net.tcp ( which seem to me have to do with my case), they are disabled.