Establishing an AR after high network load not possible in some cases

When a fragmented RPC request to the device is interrupted in the transfer, a later connection establishment might be rejected with "Out of AR Resources". The problem occurs when a fragmented RPC Connect service or RPC Write service is interrupted when the request itself has not yet been fully transferred from the controller to the device. In this case an internal resource is not released as expected.

It is expected that after a certain amount of idle time of the device, a connect is possible again. This idle time is defined by the DCE RPC layer, as timeout for an incomming, incomplete RPC service.