HighTechTalks DotNet Forums  

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

Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps


Discuss WCF: WCF service is not visible from clients outside the development computer. in the Dotnet Distributed Applications forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Mike
 
Posts: n/a

Default WCF: WCF service is not visible from clients outside the development computer. - 12-26-2007 , 11:08 AM






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

I have the following service implementation



<services>



<service name="Hitnext.ActiveDialer.Services.ActiveDialerSe rvices"

behaviorConfiguration="ServiceBehavior">



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

contract="Hitnext.ActiveDialer.Services.IActiveDia lerServices"

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?

Thanks!







Reply With Quote
  #2  
Old   
NonNB
 
Posts: n/a

Default Re: WCF: WCF service is not visible from clients outside thedevelopment computer. - 12-27-2007 , 11:11 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

Quote:
service name="Hitnext.ActiveDialer.Services.ActiveDialerSe rvices"

behaviorConfiguration="ServiceBehavior"

endpoint name="netTCP_Endpoint"
binding="netTcpBinding"

contract="Hitnext.ActiveDialer.Services.IActiveDia lerServices"

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?

Thanks!

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.