Yes I have enabled the net.tcp protocol on the website.
Main Topics
Browse All TopicsI am trying to create a simple wcf service that has a net.tcp endpoint. My OS is Vista and I am hosting the service in IIS 7. I have set my default website binding for net.tcp to 9200:* and added net.Tcp to my Enabled Protocols in my website hosting the service and the default website. Here is my Config Values:
<system.serviceModel>
<services>
<service name="FirstWcfService.Serv
<!-- Service Endpoints -->
<endpoint address="" binding="netTcpBinding" contract="FirstWcfService.
bindingConfiguration="tcpb
<endpoint address="mextcp" binding="mexTcpBinding" contract="IMetadataExchang
<endpoint address="" binding="wsHttpBinding" contract="FirstWcfService.
/>
<endpoint address="mexhttp" binding="mexHttpBinding" contract="IMetadataExchang
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="ServiceBehavior">
<!-- To receive exception details in faults for debugging purposes,
set the value below to true. Set to false before deployment to avoid
disclosing exception information -->
<serviceMetadata httpGetEnabled="true" />
<serviceDebug includeExceptionDetailInFa
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<netTcpBinding>
<binding name="tcpbinding">
<!--<security mode="None"></security>-->
<security mode="None" />
</binding>
</netTcpBinding>
</bindings>
</system.serviceModel>
The wsHttp endpoint seems to work fine. When I try to add a service reference through VS2008 to net.tcp://localhost:9200/
Metadata contains a reference that cannot be resolved: 'net.tcp://localhost:9200/
The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost:9200/
If the service is defined in the current solution, try building the solution and adding the service reference again.
Now if I add the service using the wshttp endpoint, it will add the net.tcp endpoint to my client app. But if I try to use the net.tcp endpoint, I get this error:
{"The message could not be dispatched because the service at the endpoint address 'net.tcp://XXXXXXXXX:9200/
Anyone have any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Alright, I have some new info. Thanks for the help so far. So it turns out that this is an issue related the configuration on a specific vista installation. I took the same code over to another vista machine and all works just fine. I have verified that net.tcp listeners are started and WAS is started. Also, net.tcp is included as enabled protocol for the root application and the sub-app. The settings seem identical to the machine on which it works. Does anyone know what settings may cause something like this?
Business Accounts
Answer for Membership
by: apeterPosted on 2009-01-13 at 09:22:31ID: 23364998
Have you enabled net.tcp for your site in IIS ? if not do below and try again
IIS (7.0) Admin -> Right Click on your Web Site -> Manage Website -> Advanced Settings... the "enabled protocols" should have value "net.tcp" as one of the value for tcp connection to work.