Hello - As I am trying to find a solution to this issue myself I thought I would branch out and try to tap the infinite pool of knowledge the people in this community have. Problem is I cannot get a networked host machine to get verified successfully when I click Verify on the Host tab in my Network Suite of my Master Project . See screenshot attached for error returned. Supporting info, e.g., setup: the Host machine is in our network and I can connect to it via RDP with no issues. Please see image for specific details Ive setup in TC. Any help is appreciated.

Hi there, I am using distributed testing via the NetworkSuite a lot and know the pain with it. First you should read the Article about the Requirements for distributed Testing.You have to follow those steps to get your client up and running propperly. You can find it here. It sounds like you did not configure your machine to allow unsecure RDP connections. Than the Ports that are documented are wrong. After Patching TC to Version 14 they changed the default Ports. They are now TCP 6095,6096,6097 If you are not sure about the Ports you can look them up in Tools -> Options... -> Engines -> Network Suite. I would first try to get RDP Connections running and make sure you can ping and connect to your Client from your Host. Than You need to configure the Firewall with the mentioned Ports. Cheers, Constantin

Thats really weird, since version 14 my ports changed to 6095-6097. Maybe someone from the Support Team could shed some light on this. However just stick on the Ports shown on your NetworkSuite and you should be fine. Cheers, Constantin

Hello all - well I figured I might as well provide an update, a well deserved update as so many of you have extended your helping hand to me regarding this issue. I am going to be unable to test the features and capabilities of TestComplete as they apply to Distributed / Parallel Testing processes. This is due to a setting that needs to be disabled as per the Dist Testing Requirements found here. It is item 5 Disable Secure Login. This Windows setting is under a security policy that is company-wide here. This is not something that is easy to make an exception for since it is a part of the image(s) on all machines within the network the application under test will be residing. I have found that the myriad of requirements / settings/ modifications that need to be satisfied in order for a Master Project computer for example, to communicate w a Slave Project computer(s) to be quite lengthy and technical to say the least. There are upwards of a dozen such requirements. When you compare this approach to other tools' requirements/ preparations needed to facilitate distributed testing, you become rather frustrated and very disappointed. One example, MicroFocus' ALM; the requirements are only a handful - install a 'lab agent' on all remote hosts, start the service then add machine name, a user and passwrd to the host pool page (same as the Network Suite > Hosts tab in TC) and then you're in business. No reaching out to the Security Team, Desktop Engineering in an escalation from Desktop Support and having to explain to Director level resources why you need such a change, etc... PLAN B: Im now going to look into letting the integration to TFS (via MSVS) be the controlling entity of the remote hosts, to test parallel testing capabilities of TC. Off the top of my head Im thinking of having a TC Project per Business Area of our AUT. Then creating a Build Definition for each TC Project and it will have one remote host per project. Im rather new to the world of TFS so my terminology may be off. So apologies if anyone is confused. This actually brings me to my next request, if there a thread on this topic I just explained that ya'll know of, please share the link if you dont mind. Again, thanks for all the help. Cheers, Chris

Please make sure ports 6090 and 6092 are open on Master and Slave in the firewalls Also make sure TestComplete or TestExecute (whichever you chose to use) is working correctly on the slave machine before starting the distributed test Good luck -Lino

Ive followed the setup for the firewalls - inbound and outbound rules. Ive tried those specific ports for both local and remote ports, and then All Ports for both. I get the same result. Thanks for your reply. Is there anything else I can check?

TestComplete - Network Suite - Host Verification Failure

Fimbultyr
Contributor
6 years ago
Hi there,

I am using distributed testing via the NetworkSuite a lot and know the pain with it.

First you should read the Article about the Requirements for distributed Testing.
You have to follow those steps to get your client up and running propperly.

You can find it here.

It sounds like you did not configure your machine to allow unsecure RDP connections.

Than the Ports that are documented are wrong.

After Patching TC to Version 14 they changed the default Ports.

They are now TCP 6095,6096,6097

If you are not sure about the Ports you can look them up in Tools -> Options... -> Engines -> Network Suite.

I would first try to get RDP Connections running and make sure you can ping and connect to your Client from your Host.

Than You need to configure the Firewall with the mentioned Ports.

Cheers,

Constantin
- Southpaw
  Contributor
  6 years ago
  ConstantinNeoz Thanks much for the detailed reply. I appreciate it. Im still going through the setup. But in the meantime, regarding the TCP Ports (default as shown in Tools>Options>Engines>Network Suite for the lates version of TC, mine still show the 6090 (editable), 6091,6092 (both static). Are the new default ports your reply mentions supposed to be the ports displayed in the UI?
  
  Thanks,
  
  Chris
  - Fimbultyr
    Contributor
    6 years ago
    Hi Chris,
    
    Yes the new Ports would be shown in the NetworkSuite Options as well.
    
    Just use the Ports shown in the NetworkSuite and you will be fine.
    
    I guess you have an older Version of TestComplete, just keep in mind that those could change after an update.
    
    Keep us updated if it works out for you.
    
    Cheers,
    
    Constantin
LinoTadros
Community Hero
6 years ago
Please make sure ports 6090 and 6092 are open on Master and Slave in the firewalls

Also make sure TestComplete or TestExecute (whichever you chose to use) is working correctly on the slave machine before starting the distributed test

Good luck

-Lino
- Southpaw
  Contributor
  6 years ago
  Ive followed the setup for the firewalls - inbound and outbound rules. Ive tried those specific ports for both local and remote ports, and then All Ports for both. I get the same result.
  
  Thanks for your reply. Is there anything else I can check?
  - LinoTadros
    Community Hero
    6 years ago
    I will recommend 2 more things and hope it will help you
    
    1- Try using the IP address instead of the machine name and see if that solves the problem
    
    2- Make sure the version of TestComplete and/or TextExecute are IDENTICAL between the master and the slave.
    
    Cheers
    
    Lino

Forum Discussion

TestComplete - Network Suite - Host Verification Failure

Related Content

TestComplete 8 Network Suite Verification failed Issue

Server SSL Certificate verification failed, issues is not trusted

Distributed testing - failed verification

Impact of TestComplete on Network?

TestComplete with Zephyr Scale

Recent Discussions

Problems by validating a tooltip of a wpf application

Unable to instrument the .apk application

Count number of test cases in Execution Plan

Support for Windows Server 2022

Chrome Blocking iocm.js Upon Microsoft OAuth Login Attempt