Verifying - connection error.
I have a lot of problems with Distributed Testing and Test Complete 9. I use Test Complete 9.1 trial version. I want to test if is possible to run distributed testing with Test Complete and TestExecu...
Forum Discussion
Hi SmartBear heroes!
Distributed testing from my Win7 machine, which is on our company domain, I can do! To a machine that is not connected to our domain, that is... However, setting up a host in TestComplete for the actual Win7 test-machine that is (has to be) connected to the company domain, results in the Verification failed, Host1 (ipaddress): Communication error, (which eventually now, fills me with dread more and more...). ;-)
I have gone though the Message Verification Failed troubleshooting page, I have tried many combinations for domain and username (also with domain\username for example) and I keep hitting this commucation error wall.
If I try 'normal' remote desktop from my machine (mstsc.exe) the dialogs accept the IP address of the Win7 test-machine and ourDomain\myUsername as user name to connect and after this my password is asked in the Windows Security dialog. Obtaining a Remote Desktop Session works because my account is administrator for this Win7 test-machine. I did try adding my account locally to the Remote Desktop User group, aditionally. Furthermore I tried testing with a local account on the Win7 test-machine, that was als added to the Desktop User Group... bu still no luck.
Many thanks in advance for any tips!
Distributed testing from my Win7 machine, which is on our company domain, I can do! To a machine that is not connected to our domain, that is... However, setting up a host in TestComplete for the actual Win7 test-machine that is (has to be) connected to the company domain, results in the Verification failed, Host1 (ipaddress): Communication error, (which eventually now, fills me with dread more and more...). ;-)
I have gone though the Message Verification Failed troubleshooting page, I have tried many combinations for domain and username (also with domain\username for example) and I keep hitting this commucation error wall.
If I try 'normal' remote desktop from my machine (mstsc.exe) the dialogs accept the IP address of the Win7 test-machine and ourDomain\myUsername as user name to connect and after this my password is asked in the Windows Security dialog. Obtaining a Remote Desktop Session works because my account is administrator for this Win7 test-machine. I did try adding my account locally to the Remote Desktop User group, aditionally. Furthermore I tried testing with a local account on the Win7 test-machine, that was als added to the Desktop User Group... bu still no luck.
Any idea what might be keeping me from success?
Is there maybe logging from TestComplete related to the NetworkSuite, that I can check for the possible cause (for all I know I entered my password incorrectly the many times I re-entered my password ...
not very likely though)
Many thanks in advance for any tips!