dotnet web services: 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?

"Mike" <mike@hitnext.com> wrote in
news:31624CECC46E49D4A3320714DC18D75E@PHBASE:

[quoted text, click to view]

Have you checked your server's firewall? Can you connect externally?

--