tcp timeout

microsoft.public.dotnet.framework

7 Mar 2006 10:35 PM

Jim

I'm using .NET 2.0 Remoting with tcp. I am using configuration files. I've
run into a problem where my client program waits for over a minute before it
times out if the server is not running.

I tried to control this through the configuration file, but it doesn't seem
to have any affect.

Also, is there a different between the timeout when you first establish a
connection, and a timeout when you actually make the remoting call?

Thanks,

Jim

-------
Here is my client's configuration file:

<configuration>
<system.runtime.remoting>
<application>
<client>
<wellknown type="TestServer.TestServer, TestServer"
url="tcp://localhost:46232/TestServer.rem" />
</client>
<channels>
<channel ref="tcp" timeout="5000" />
</channels>
</application>
</system.runtime.remoting>
</configuration>