Reference KB: http://support.citrix.com/article/CTX133877
when a plurality of stream server NIC assigned to PVS, the following symptoms Provisioning Services (PVS) server.
Case
NIC streaming environments with five of the following symptoms:
When the display device is connected click on the PVS console, the following symptoms may be experienced:
the server time-out error 4002
List of abnormal delay connection device 3-4 minutes
PVS console stops responding
image User-added 
solution
carefully! Before using the Registry Editor, please see disclaimer at the end of this article.
Complete the following actions to resolve this problem:
1, on the PVS Server computer \ software \ citrix \ provisioningServices \ item under HKLM Manager, create a registry DWORD RelayedRequestReplyTimeoutMilliseconds, and set it to 50 ms.
Note: Be sure to select decimal, not hexadecimal.
2, create a DWORD RelayedRequestTryTimes and set it to 1.
The default value is 2.
3. Open the PVS server console and select Show Connected Devices command for testing.
Problem Cause
command console runs from PVS Show Connected Devices, which sends the request to each interface bound to the streaming service, sent to each target device, the default timeout is 5000 milliseconds, each NIC twice, resulting in search time for each device, each device 10 seconds.
Example:
5 NIC, 1 target device is currently connected to the return Show Connected Device in 50 seconds.
You can clearly see it in the log flow is searching for an IP address assigned to each of the streaming service:
2012-05-25 10: 05: 24,614 [0x00000fdc ] DEBUG CManagerConfig :: GetRelayedRequestTryTimes - <RelayedRequestTryTimes> = 2 2012-05-25 10: 05: 24,614 [0x00000fdc] DEBUG CManagerConfig :: GetRelayedRequestReplyTimeoutMilliseconds - <RelayedRequestReplyTimeoutMilliseconds> = 5000 2012- 05-31 14: 47: 46,470 [0x00000e7c ] DEBUG CManagerConfig :: GetServerIpGroupTryTimes - <ServerIpGroupTryTimes> = 2 2012-05-31 14: 47: 46,470 [0x00000e7c] DEBUG CManagerConfig :: GetServerReplyTimeoutMilliseconds - <ServerReplyTimeoutMilliseconds> = 50000 2012-05- 31 14: 47: 46,470 [0x00000e7c ] debug CManagerReplyReceiver: SendMessageToServer, the requestId = 0
2012-05-31 14: 47: 46,486 [0x00000e7c] in debugging CManagerReplyReceiver: TryEachIpAddressIteratively
2012-05-31 14: 47: 46,486 [0x00000e7c] the dEBUG attempts to send a request to the ip address = 2887140615, port = 6911
2012-05-31 14: 47: 46,486 [0x00000e7c ] Debug CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 47: 46,501 [0x00000e7c] Add the DEBUG request ID 0 future
2012-05-31 14: 47: 46,501 [0x00000e7c ] to the DEBUG <172.22.69.7:6911>, 80 bytes to be sent
2012-05-31 14: 47: 46,501 [0x00000e7c ] DEBUG 80 bytes 80 bytes transmitted message
2012-05-3114: 47: 56,516 [0x00000e7c] DEBUG futureResult.get failed, error 121 =
2012-05-31 14: 47: 56,516 [0x00000e7c] remote request timeout error
2012-05-31 14: 47: 56,532 [0x00000e7c ] DEBUG for requestId = 0, return a result = -32718 (RemoteRequestTimedOut). wait.
2012-05-31 14: 47: 56,532 [0x00000e7c ] number of entries in DEBUG futureMap 0 =
2012-05-31 14: 47: 56,532 [0x00000e7c ] the DEBUG 2887140359 attempts to send a request address = IP, Port = 6911
2012- 05-31 14: 47: 56,532 [0x00000e7c ] debug CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 47: 56,532 [0x00000e7c ] DEBUG request ID 0 is added next
2012-05-31 14: 47: 56,532 [0x00000e7c ] DEBUG to <172.22.68.7:6911>, 80 bytes to be sent
2012-05-31 14: 47: 56,532 [0x00000e7c ] DEBUG 80 bytes 80 bytes transmitted message
2012-05-31 14: 48: 06,547 [0x00000e7c ] DEBUG futureResult.get failed, error = 121
2012-05-31 14: 48: 06,547 [0x00000e7c] ERROR remote request timeout
2012-05-31 14: 48: 06,547 [0x00000e7c ] DEBUG for requestId = 0, return result = -32718 (RemoteRequestTimedOut). wait.
2012-05-31 14: 48: 06,547 [0x00000e7c ] number of entries in DEBUG futureMap 0 =
2012-05-31 14: 48: 06,547 [0x00000e7c ] the DEBUG 2887140103 attempts to send a request address = IP, Port = 6911
2012- 05-31 14: 48: 06,547 [0x00000e7c ] in debugging CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 48: 06,547 [0x00000e7c] requests the dEBUG ID 0 is added in the future
2012-05-31 14: 48: 06,547 [0x00000e7c ] DEBUG to <172.22.67.7:6911>, 80 bytes to be sent
2012-05-31 14: 48: 06,547 [0x00000e7c ] DEBUG transmitting 80-byte word 80 section message
2012-05-31 14: 48: 16,562 [0x00000e7c ] DEBUG futureResult.get failed, error 121 =
2012-05-31 14: 48: 16,562 [0x00000e7c] remote request timeout error
2012-05-31 14:48: 16,562 [0x00000e7c] DEBUG for requestId = 0, return result = -32718 (RemoteRequestTimedOut). wait.
2012-05-31 14: 48: 16,562 [0x00000e7c ] number of entries in DEBUG futureMap 0 =
2012-05-31 14: 48: 16,562 [0x00000e7c ] ip address the DEBUG will attempt to send a request 2,887,139,847 =, Port = 6911
2012- 05-31 14: 48: 16,562 [0x00000e7c ] in debugging CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 48: 16,562 [0x00000e7c] Add the dEBUG request ID 0 future
2012-05-31 14: 48: 16,562 [0x00000e7c ] to the DEBUG <172.22.66.7:6911>, 80 bytes to be sent
2012-05-31 14: 48: 16,562 [0x00000e7c ] DEBUG 80 bytes 80 bytes transmitted message
2012-05-31 14: 48: 26,577 [0x00000e7c ] DEBUG futureResult.get failed, error = 121
2012-05-31 14: 48: 26,577 [0x00000e7c] remote request timeout error
2012-05-31 14: 48: 26,577 [0x00000e7c ] DEBUG for requestId = 0, return a result = -32718 (RemoteRequestTimedOut). wait.
2012-05-31 14: 48: 26,577 [0x00000e7c ] number of entries in DEBUG futureMap 0 =
2012-05-31 14: 48: 26,577 [0x00000e7c ] the DEBUG will attempt to send a request to the ip address 2887139591 =, Port = 6911
2012- 05-31 14: 48: 26,577 [0x00000e7c ] debug CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 48: 26,577 [0x00000e7c ] dEBUG request ID 0 is added next
2012-05-31 14: 48: 26,577 [0x00000e7c ] dEBUG to <172.22.65.7:6911>, 80 bytes to be sent
2012-05-31 14: 48: 26,577 [0x00000e7c ] DEBUG transmitted message bytes 80 bytes 80
2012-05-31 14: 48: 36,592 [0x00000e7c ] DEBUG futureResult.get failed, error 121 =
2012-05-3114: 48: 36,592 [0x00000e7c] Remote Request Timeout Error
2012-05-3114: 48: 36,592 [ 0x00000e7c] DEBUG for requestId = 0, return a result = -32718 (RemoteRequestTimedOut). wait.
2012-05-31 14: 48: 36,592 [0x00000e7c ] number of entries in DEBUG futureMap 0 =
2012-05-31 14: 48: 36,592 [0x00000e7c ] = 2,887,139,335 the DEBUG will try to send a request address IP, Port = 6911
2012- 05-31 14: 48: 36,592 [0x00000e7c ] debug CManagerReplyReceiver: sendMessageAndWaitForResult
2012-05-31 14: 48: 36,592 [0x00000e7c ] dEBUG request ID 0 is added next
2012-05-31 14: 48: 36,592 [0x00000e7c ] dEBUG to <172.22.64.7:6911>, 80 bytes to be sent
2012-05-31 14: 48: 36,592 [0x00000e7c ] DEBUG 80 bytes 80 bytes transmitted message
2012-05-31 14: 48: 37,247 [0x000030fc ] debugging CManagerReplyReceiver :: dispatchPacket
2012-05-31 14: 48: 37,247 [0x000030fc ] DEBUG header opcode = -2147221501, 0 = request ID
2012-05-31 14: 48: 37,247 [0x000030fc ] DEBUG processing ManagedServer Reply
2012-05-3114: 48: 37,247 [0x000030fc] CREMoteManagedServer :: handleReply in the DEBUG
2012-05-31 14: 48: 37,247 [0x000030fc] the DEBUG processing request reply id = 0
2012-05-31 14: 48: 37,263 [0x000030fc ] DEBUG found requestId future
2012-05-31 14: 48: 37,263 [0x000030fc ] DEBUG conversion rebalancing replies to replies state, the default success
2012-05-31 14: 48: 37,278 [0x000030fc ] CREMoteManagedServer :: harvestReplyDataFromMessage in DEBUG
2012-05 -31 14: 48: 37,278 [0x000030fc ] DEBUG reply request for re-balancing, the requestId = 0
2012-05-31 14: 48: 37,278 [0x000030fc] a reply from the DEBUG value of 21
2012-05-31 14:48: 37,278 [0x000030fc] DEBUG entry is added to the data results requestId = 0 of FIG.
2012-05-31 14: 48: 37,294 [0x00000e7c] DEBUG futureResult.get of requestId = 0, actualResult = 0 (success) success. wait.