Minimum Idle Connection Timeout for RPC/HTTP connections

Directs the RPC Runtime to assume the specified timeout as the idle connection timeout even if the IIS server running the RPC HTTP proxy is configured with a higher timeout. If the IIS server running the RPC HTTP proxy is configured with a lower idle connection timeout, the timeout on the IIS server is used. The timeout is given in seconds.

This setting is useful in cases where a network agent like an HTTP proxy or a router uses a lower idle connection timeout than the IIS server running the RPC HTTP proxy. In such cases RPC over HTTP clients may encounter errors because connections will be timed out faster than expected. Using this setting you can force the RPC Runtime and the RPC Proxy to use a lower connection timeout.

This setting is only applicable when the RPC Client, the RPC Server and the RPC HTTP Proxy are all running Windows Server 2003 family/Windows XP SP1 or higher versions. If either the RPC Client or the RPC Server or the RPC HTTP Proxy run on an older version of Windows, this setting will be ignored.

The minimum allowed value for this setting is 90 seconds. The maximum is 7200 (2 hours).

If you disable this setting or do not configure it, the idle connection timeout on the IIS server running the RPC HTTP proxy will be used.

Note: This policy setting will not be applied until the system is rebooted.

Supported on: At least Windows Server 2003 operating systems or Windows XP Professional with SP1

Minimum Idle Connection Timeout (in seconds):

Registry PathSoftware\Policies\Microsoft\Windows NT\Rpc
Value NameMinimumConnectionTimeout
Default Value900
Min Value90
Max Value


Administrative Templates (Computers)

Administrative Templates (Users)