Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Right now your service endpoint address is:</p> <p><code>net.tcp://jerrycan:8000/service</code></p> <p>When you create clients on the computer which is hosting the service (jerrycan-pc) of course the local clients will be able to access the service by referencing </p> <p><code>net.tcp://localhost:8000/service</code></p> <p>and obviously other clients (on other computers on your network) <strong>can not</strong> connect to the service if they try to contact <strong>localhost</strong>, because the endpoint: <code>net.tcp://localhost:8000/service</code>, is calling the local computer which in this case is not hosting the service (only for jerrycan-pc). If <code>jerrycan-pc</code> is hosting the service, clients on <code>jerrycan-pc</code> can call the service by referencing <code>localhost</code>, but clients on say <code>mike-pc</code> must either try to call <code>jerrycan-pc</code> or <code>jerrycan-pc</code>'s IP. If you change the endpoint in your service configuration to your service hosts IP or even computer name, and reference the service on other computers using the IP of the service host/computer name then they will be able to access it. For example if jerrycan-pc is hosting the service and it has an IP of <code>192.168.1.5</code>, your clients can consume the service by referencing this endpoint:</p> <p><code>net.tcp://192.168.1.5:8000/service</code></p> <p>So in your service config change <code>localhost</code> to the IP address or PC name and try to contact that address on your clients instead of contacting <code>localhost</code>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload