Suppose an administrator offers Remote Assitance to a client: Admin ---(arbitrary port to TCP 135)--->> User Admin <<-(TPC 135 to arbitrary port)----- User After a brief conversation, the User computer will specify the port on which its msra.exe will listen, like any other DCOM/RPC service, and the conversation will continue, e.g., Admin ---(arbitrary port to msra.exe on TCP 49523)--->> User The listening port is selected from the general range of ephemeral ports, starting (by default) at 49152 and ending at 65535. We don't want this, so we limit our ephemeral port range... netsh int ipv4 set dynamicport tcp start=49152 num=3000 and we specify a relatively small range of ports specifically for RPC: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet Ports = "65000-65535" PortsInternetAvailable = "y" UseInternetPorts = "y" We expect Remote Assistance to use the RPC-specific range. Unfortunately, it does not. This is very frustrating. We'd like to very narrowly restrict the range of ports on which msra.exe can listen, but there doesn't appear to be any way to do that. The ephemeral port range needs to be pretty big. The range of possible listening ports for msra.exe should be very small--ideally, 1. Is there a way to set the port range for Remote Assistance? Is there at least a way to force it to choose ports out of the defined RPC port pool? Please enlighten me if I'm misunderstanding the situation. Thanks for any help. ..Jeff

Let me know if you find this solution, I have scoured every site conceivable to find this solution and have found nothing.