Comments on: Resolving conflict: Http ports and XPSP2

By: Kenny

Kenny — Tue, 09 Mar 2010 09:05:21 +0000

Godwin, if you want to use port 80 on XPSP2 then you need to disable IIS or change the port that it’s using.

By: Kenny

Kenny — Tue, 09 Mar 2010 09:04:41 +0000

echoe, let me provide some counterpoint here.
1) NetTcpBinding is intended to be used within a corporation/network (i.e. intranet). For most internet-based communication you need to use HTTP as that’s what’s widely deployed and supported through proxies, etc. NetTcp was never intended to replace all uses of TCP
2) WsHttpDualBinding was intended for scenarios where both sides are globally addressable (such as B2B communication). It was not intended to address NAT traversal.

For what you are desiring (i.e. bidrectional communication behind a NAT/firewall), you’ll want something like the HTTP polling duplex channel that’s shipped in Silverlight. It uses a client-based HTTP polling mechanism to allow bidirectional communication to occur even though it’s always “initiated” by the client from the HTTP perspective.

By: Kenny

Kenny — Tue, 09 Mar 2010 09:01:13 +0000

Santhosh, it sounds like you need to setup proxy authentication on your binding.
Huong, Environment.MachineName will help you out

By: Harin

Harin — Wed, 03 Feb 2010 14:23:53 +0000

Great. Thanks.

By: Kenny

Kenny — Wed, 03 Feb 2010 01:01:52 +0000

Venemo, Environment.MachineName will help you out. Peter, I wonder if you need to add a firewall exception.

By: Kenny

Kenny — Wed, 03 Feb 2010 01:00:26 +0000

You can use the same port number as long as the base URI paths are distinct.

By: Harin

Harin — Tue, 02 Feb 2010 22:06:00 +0000

If I have more than one client, will I have to come up with a different port number for each client?

By: Santhosh

Santhosh — Mon, 18 Jan 2010 09:01:01 +0000

Sir I have a windows application running which starts WCF service. Another windows application has to interact with the WCF service. Now my error is

The remote server returned an unexpected response: (407) Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. )

In local system it works fine but in remote application it is not working.

Please help me in this problem.

By: Huong

Huong — Wed, 11 Nov 2009 10:18:11 +0000

Can any one give me the idea of how to get clientmachinename when deploy the application?
Strange that, when i set clientbaseaddress to http://specifiedclientname:3001/Service/ then my application works well, but when set to http://ipaddress:3001/Service/ then it doesn’t work. (specifiedclientname, and ipaddress identify one computer)

By: echoe

echoe — Thu, 29 Oct 2009 22:28:44 +0000

Sirs, my conclusions on WCF:

* In WCF, if you need bidirectional communication, you have two options: netTcpBinding and wsDualHttpBinding.
* netTcpBinding may not work behind firewalls, it depends on your client’s security policies.
* If your client lives behind network Proxy (i.e. squid), you cannot use netTcpBinding.
* But guess what? wsDualHttpBinding is Proxy enabled, great!

…ejem, no… If your client is in a private network behind a proxy, something very common, the server will never be able to see the client: that’s the idea of a proxy firewall my friends. That’s what you may be suffering, no? based on what I read from some posts here.

Conclusion: wsDualHttpBinding is completely USELESS and netTcpBinding is almost as USELESS, while being impossible for any of them to work behind a network Proxy.

Microsoft, com’on? Don’t you have the resources to solve that? Do you think we will adventure in WCF just to do either LAN applications or web sites?