This question is in follow up to this previously asked question. Where VS Loadtest fails when submitted to a controller, the reason for failure being "No such Host is known". My setup is nearly the same:
- Azure configured with a 10. network
- 1 Test Controller in Azure (in AD)
- 2 Test Agents in Azure (in AD)
- 1 VS 2013 instance on the local desktop (remote to azure network)
- Local machine attached to the Azure network via point-to-site VPN
- The local machine is not part of Azure VM's AD
- Use "Credential Manager" to specify domain credentials connecting to the controller host
- VS2013 client is able to connect and even restart controllers/agents
VS Client Host can resolve controller host name using FQDN controller.domain.local
Agents connect to the controller using same FQDN
From what I have been gathering this issue is caused by the CONTROLLERS inability to resolve the VS-Client Host's address. Is that correct? The attached link hints towards a hotfix but does not provide one. Additionally since i am using the P2S VPN there is no static IP mapping for clients so i am unable to add a record in the Hosts file to point the controller towards the client.
Am I understanding the issue correctly, Has there been any resolution to this issue?
