How to test WCF net.tcp when http works?

Question

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?

I'm not sure if I'm doing it right. At the commend prompt, I type in "telnet 51056". I get a blank screen. — 4thSpace, Jul 15 '15 at 19:23
That means the connection works. What does http://localhost:51056 do in the browser? — usr, Jul 15 '15 at 19:43
I would set up tracing to see what is really going on in details. — jsanalytics, Jul 15 '15 at 23:24
Tracing details don't add anything. I see entries where the app is trying to call methods on the service but the throw the same EndpointNotFoundException. So not additional info. — 4thSpace, Jul 16 '15 at 17:44

score 0 · Answer 1 · edited May 23 '17 at 12:21

0

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

edited May 23 '17 at 12:21

Community

answered Jul 16 '15 at 06:19

pkk

1 Answers1