With netTCP binding TCP error code 10061: No connection could be made because the target machine actively refused it

With netTCP binding TCP error code 10061: No connection could be made
because the target machine actively refused it

I have my WCF service with Self Hosting on netTCP:
<system.serviceModel>
<services>
<service behaviorConfiguration="Test"
name="WcfService1.Service1">
<host>
<baseAddresses>
<add
baseAddress="net.tcp://127.0.0.1:808/Service1.svc"/>
</baseAddresses>
</host>
<endpoint address="" binding="netTcpBinding"
bindingConfiguration="NetTcpEndpointBinding"
contract="WcfService1.IService1">
<identity>
<dns value="127.0.0.1" />
</identity>
</endpoint>
<!--<endpoint address="mex" binding="mexTcpBinding"
contract="IMetadataExchange" bindingConfiguration="" />-->
</service>
</services>
<bindings>
<netTcpBinding>
<binding name="NetTcpEndpointBinding"
portSharingEnabled="true" maxConnections="1000">
<security mode="Transport">
<transport clientCredentialType="Windows" />
</security>
</binding>
</netTcpBinding>
</bindings>
<protocolMapping>
<add scheme="net.tcp" binding="netTcpBinding"/>
</protocolMapping>
<behaviors>
<serviceBehaviors>
<behavior name="Test">
<serviceAuthenticationManager
authenticationSchemes="IntegratedWindowsAuthentication"
/>
<!-- To avoid disclosing metadata information, set the
values below to false before deployment -->
<serviceMetadata httpGetEnabled="false"
httpsGetEnabled="false" />
<!-- 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 -->
<serviceDebug includeExceptionDetailInFaults="false" />
<serviceThrottling maxConcurrentCalls="400"
maxConcurrentInstances ="400" maxConcurrentSessions
="400"/>
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true"
multipleSiteBindingsEnabled="true" />
</system.serviceModel>
But as soon as I run the client ,I am getting the following error:
TCP error code 10061: No connection could be made because the target
machine actively refused it 127.0.0.1:808
I have enabled the port 808. What else is missing?