all groups > dotnet distributed apps > december 2007 >
You're in the

dotnet distributed apps

group:

WCF: WCF service is not visible from clients outside the development computer.


WCF: WCF service is not visible from clients outside the development computer. Mike
12/26/2007 12:08:23 PM
dotnet distributed apps: WCF service is not visible from clients outside the development
computer.

I have the following service implementation



<services>



<service name="Hitnext.ActiveDialer.Services.ActiveDialerServices"

behaviorConfiguration="ServiceBehavior">



<endpoint name="netTCP_Endpoint"
binding="netTcpBinding"

contract="Hitnext.ActiveDialer.Services.IActiveDialerServices"

bindingConfiguration="netTCP_Bindings"/>



<endpoint name="MetaDataEchange"

binding="mexHttpBinding"

contract="IMetadataExchange" />



<host>

<baseAddresses>

<add baseAddress="net.tcp://somedomain.com:19000" />

<add baseAddress="http://localhost:18000" />

</baseAddresses>

</host>



</service>



</services>



I create a proxy in the client side thru the Add Service Reference tool
in VS.
When I run it from my computer (local development computer) it works
fine.

If I publish the app and try to run it from another computer, it does
not find the service (that is running in somedomain.com:19000).

So you know the service is running when I run the client, and I can
access somedomain.com:19000 via telnet from the client computer. And
also I redirect connection from ports 19000 and 18000 to the computer
running the service.

Any idea why it might now be working?

Re: WCF: WCF service is not visible from clients outside the development computer. NonNB
12/27/2007 9:11:43 PM

Hi

If you can telnet, it is probably the client at fault.

It might be because the mex is http but the service netTcp?

HTH
Stuart

[quoted text, click to view]
Re: WCF service is not visible from clients outside the development computer. Onawole Clement Oladapo
2/6/2008 1:31:50 PM
Do you have a firewall running on your host machine. Windows firewall =
when on do block such incoming communications. U can disable the =
firewall to check if it works (Not recommended).

The recommended way if this is your situation is to create an exception =
in the firewall allowing communication on the used ports
[quoted text, click to view]
WCF service is not visible from clients outside the development =
computer.

I have the following service implementation

=20

<services>

=20

<service name=3D"Hitnext.ActiveDialer.Services.ActiveDialerServices"

behaviorConfiguration=3D"ServiceBehavior">

=20

<endpoint name=3D"netTCP_Endpoint"=20
binding=3D"netTcpBinding"

contract=3D"Hitnext.ActiveDialer.Services.IActiveDialerServices" =


bindingConfiguration=3D"netTCP_Bindings"/>

=20

<endpoint name=3D"MetaDataEchange"

binding=3D"mexHttpBinding"

contract=3D"IMetadataExchange" />

=20

<host>

<baseAddresses>

<add baseAddress=3D"net.tcp://somedomain.com:19000" />

<add baseAddress=3D"http://localhost:18000" />

</baseAddresses>

</host>

=20

</service>

=20

</services>

=20

I create a proxy in the client side thru the Add Service Reference =
tool in VS.
When I run it from my computer (local development computer) it works =
fine.

If I publish the app and try to run it from another computer, it does =
not find the service (that is running in somedomain.com:19000).

So you know the service is running when I run the client, and I can =
access somedomain.com:19000 via telnet from the client computer. And =
also I redirect connection from ports 19000 and 18000 to the computer =
running the service.

Any idea why it might now be working?

Thanks!

=20

AddThis Social Bookmark Button