net.tcp failure

We have an ASP.NET web site that has a WCF client connection to a Windows
service that has some indexed data that the web app is querying. The service
has two endpoints: a named pipes endpoint and a TCP endpoint. In the
development environment, both endpoints connected and performed great with
both IIS and the Windows service on the workstation, and both endpoints
connected and performed equally great using the TCP endpoint with the
Windows service running on another development machine on the LAN.

While staging deployment of IIS and the Windows service on the same staging
server, though, I'm getting error message

"The socket connection was aborted. This could be caused by an error
processing your message or a receive timeout being exceeded by the remote
host, or an underlying network resource issue."

The net.pipe endpoint works fine, it's only when I switch to the net.tcp
endpoint that I get this error. I have double-verified that the DLLs match
up between IIS and the Windows service, including by re-compiling and
re-deploying, with nothing missing--the data structures shouldn't mismatch,
though, anyway, if net.pipe works with the same service. The network adapter
has two Ethernet adapters, one Internal and one External; I configured the
TCP URI initially to "localhost", same as in development, and also tried
explicitly setting it to the internal IP address on both sides (IIS and
Windows service), but I still get this error. There are no other known TCP /
Ethernet issues on this server.

Any ideas?

- Jon

Also, should mention, security is disabled (for now).

<security mode="None" />

Jon


"Jon Davis" <jon@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:uLIru1ErHHA.4180@TK2MSFTNGP04.phx.gbl...
> We have an ASP.NET web site that has a WCF client connection to a Windows
> service that has some indexed data that the web app is querying. The
> service has two endpoints: a named pipes endpoint and a TCP endpoint. In
> the development environment, both endpoints connected and performed great
> with both IIS and the Windows service on the workstation, and both
> endpoints connected and performed equally great using the TCP endpoint
> with the Windows service running on another development machine on the
> LAN.
>
> While staging deployment of IIS and the Windows service on the same
> staging server, though, I'm getting error message
>
> "The socket connection was aborted. This could be caused by an error
> processing your message or a receive timeout being exceeded by the remote
> host, or an underlying network resource issue."
>
> The net.pipe endpoint works fine, it's only when I switch to the net.tcp
> endpoint that I get this error. I have double-verified that the DLLs match
> up between IIS and the Windows service, including by re-compiling and
> re-deploying, with nothing missing--the data structures shouldn't
> mismatch, though, anyway, if net.pipe works with the same service. The
> network adapter has two Ethernet adapters, one Internal and one External;
> I configured the TCP URI initially to "localhost", same as in development,
> and also tried explicitly setting it to the internal IP address on both
> sides (IIS and Windows service), but I still get this error. There are no
> other known TCP / Ethernet issues on this server.
>
> Any ideas?
>
> - Jon
>
>

.... which brought me to the realization that I forgot to add the custom
BindingConfiguration on the Windows service config file.

<bindings>
<netTcpBinding>
<binding name="tcp_Unsecured">
<security mode="None" />
</binding>
</netTcpBinding>
</bindings>


"Jon Davis" <jon@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:u4Em1CFrHHA.3380@TK2MSFTNGP03.phx.gbl...
> Also, should mention, security is disabled (for now).
>
> <security mode="None" />
>
> Jon
>
>
> "Jon Davis" <jon@REMOVE.ME.PLEASE.jondavis.net> wrote in message
> news:uLIru1ErHHA.4180@TK2MSFTNGP04.phx.gbl...
>> We have an ASP.NET web site that has a WCF client connection to a Windows
>> service that has some indexed data that the web app is querying. The
>> service has two endpoints: a named pipes endpoint and a TCP endpoint. In
>> the development environment, both endpoints connected and performed great
>> with both IIS and the Windows service on the workstation, and both
>> endpoints connected and performed equally great using the TCP endpoint
>> with the Windows service running on another development machine on the
>> LAN.
>>
>> While staging deployment of IIS and the Windows service on the same
>> staging server, though, I'm getting error message
>>
>> "The socket connection was aborted. This could be caused by an error
>> processing your message or a receive timeout being exceeded by the remote
>> host, or an underlying network resource issue."
>>
>> The net.pipe endpoint works fine, it's only when I switch to the net.tcp
>> endpoint that I get this error. I have double-verified that the DLLs
>> match up between IIS and the Windows service, including by re-compiling
>> and re-deploying, with nothing missing--the data structures shouldn't
>> mismatch, though, anyway, if net.pipe works with the same service. The
>> network adapter has two Ethernet adapters, one Internal and one External;
>> I configured the TCP URI initially to "localhost", same as in
>> development, and also tried explicitly setting it to the internal IP
>> address on both sides (IIS and Windows service), but I still get this
>> error. There are no other known TCP / Ethernet issues on this server.
>>
>> Any ideas?
>>
>> - Jon
>>
>>
>
>