How to test WCF net.tcp when http works?

1
votes

I have a WCF service setup in IIS. I can browse fine to the HTTP endpoint (http://localhost with no port#) in a web browser.

My app is using net.tcp//localhost:51056. I keep getting an error about

The message could not be dispatched because the service at the endpoint address xxx is unavailable for the protocol of the address.

The exception is a

EndpointNotFoundException

net.tcp is setup for the service in IIS.

There is no way to test a net.tcp endpoint that I'm aware of. This use to work. Any ideas how I can trouble shoot what is wrong?

1
c#asp.net.netwcftcp
Can you telnet to the endpoint? – usr
I'm not sure if I'm doing it right. At the commend prompt, I type in "telnet <machine-name> 51056". I get a blank screen. – 4thSpace
That means the connection works. What does localhost:51056 do in the browser? – usr
The page can't be displayed. – 4thSpace
I would set up tracing to see what is really going on in details. – jsanalytics

1 Answers

0
votes

if http is working and net.tcp not. you may want to setup/check setup net.tcp binding at IIS level. take look at Enabling net.tcp in IIS7