title: WCF client and server
body: <p>I need multiple clients that talk to a WCF service. The WCF service also must be able to connect to any one of the clients also.</p>
  
  <p>So - it sounds like the server and the clients need to have both a WCF server and client built into each one.</p>
  
  <p>Is this correct or is there some way to do this?</p>
  
  <p>I was looking at NetPeerTcpBinding, but that is obsolete. To be fair I'm not sure if that is a valid solution either.</p>
  
  <p>Background:</p>
  
  <ul>
  <li>I plan to have a Windows service installed on hundreds of machines in our network with a <a href="http://en.wikipedia.org/wiki/Windows_Communication_Foundation" rel="noreferrer">WCF</a> service and a WCF client built in.</li>
  <li>I will have one Windows service installed on a server with a WCF service and a client built in.</li>
  <li>I will have a <a href="http://en.wikipedia.org/wiki/Windows_Forms" rel="noreferrer">Windows Forms</a> application</li>
  <li>I will have a database</li>
  </ul>
  
  <p>The clients on the network will connect to the service running on the server in order to insert some information on the database.</p>
  
  <p>The user will use the Windows Forms application to connect to the Windows service on the server and this Windows service will connect to the relevant client on the factory floor (to allow remote browsing of files and folders).</p>
  
  <p>Hence I believe the machines on the floor and the server both require a WCF cleint and service built in.</p>