Hi Alexey,
You are right, the port is used indeed. However, it is used by RPC Port Mapper. When an RPC connection is established, local RPC service sends a request to remote RPC service on this port. After that RPC Port Mapper on the remote machine sends the port number which will be used for further communication. This port number cannot be controlled from application's side.
If you suspect that the problem is related to firewall settings, you can try limiting the port number range used by RPC Port Mapper, and explicitly allowing communication for this port range. It should be possible to limit the port range used by RPC Endpoint Mapper, but I have found the steps only for server OS versions:
http://technet.microsoft.com/en-us/library/cc732839.aspxProbably, your network administrator may help you set this up for WinXP.
If configuring the firewall does not help, let's try to isolate the problem:
- What happens if you try to verify a Slave VM located in the same VLAN?
- Does it work if you try to verify a different VM in that another VLAN?
- Try setting up the Remote Event Log service to work between the Master and Slave computers (it also uses RPC) - this will help to check whether the problem is specific to TestComplete. You will find a description of how this can be configured in the following Microsoft TechNet article:
http://technet.microsoft.com/en-us/library/cc732839.aspxLet me know about the results.
