This is usually a problem with the network and port 135, just because the port is ''listening'' does not mean that ALM can see it.

The best way that I have been able to track it down in the past is using ''telnet'' ( a windows service) first make sure telnet is installed as a feature in windows, then open a command prompt (on the ALM machine that you are trying to kick off the test from) then type the command ''telnet UFTMachineName 135'' this should tell us if the alm machine can see port 135 on the UFT machine. If not you need to get your network guys to take a look at the machine.

Also sometimes I have had luck using the local ip address instead of the machine name when telling it where to run, sometimes it can be a DNS issue.

Additionally the machine MUST be on the same domain, if not the network guys would need to establish a domain trust so that ALM can see port 135 on that machine.

http://blog.industrialnetworking.com/2011/09/using-telnet-to-test-open-ports.html