Forum Discussion

allenj2020's avatar
allenj2020
Contributor
9 years ago

Distributed host, Verification Failed: Communication Error even in Manual mode

I have a large existing test project, but am just starting to try to split it between multiple computers. I created a master project in the suite, added NetworkSuite to master and slave, and added a...
  • allenj2020's avatar
    allenj2020
    9 years ago

    Update: A short support call determined that the ports were the problem.

    After changing the ports on the remote machine with TestExecute from 1,2,3 to 6090,6091,6092 (same as the master machine), the remote machine verified successfully, with no changes to paths.

    The rep said that they have seen this happen sometimes where the ports get set incorrectly by default, they haven't been able to reproduce the cause of it.

    Also on the host machine, in Allow Remote Access, he had me uncheck 'Allow connections only from computers running Remote Desktop with Network Level Authentication', although I don't think this was the cause of the problem.

     

    Thanks.

    Allen

allenj2020's avatar
allenj2020
Contributor

Yes, the project is on a shared drive.  I've been running my tests on a separate PC with TestExecute, accessing the main project files on my PC over a shared drive.

 

However, I also tried setting my distributed host paths to refer to local drives only, it didn't seem to make any difference.

allenj2020's avatar
allenj2020
Contributor
9 years ago

Update: A short support call determined that the ports were the problem.

After changing the ports on the remote machine with TestExecute from 1,2,3 to 6090,6091,6092 (same as the master machine), the remote machine verified successfully, with no changes to paths.

The rep said that they have seen this happen sometimes where the ports get set incorrectly by default, they haven't been able to reproduce the cause of it.

Also on the host machine, in Allow Remote Access, he had me uncheck 'Allow connections only from computers running Remote Desktop with Network Level Authentication', although I don't think this was the cause of the problem.

 

Thanks.

Allen