测试代理无法连接到 Windows Azure 上的测试控制器
我想在云上创建一个测试平台。我创建了一个 Windows azure 托管服务，用于安装测试控制器并使用本地数据库对其进行配置。我创建了另一个安装测试代理的托管服务。我通过提供从 azure 门户获取的激活令牌，在 Azure 服务中启用了虚拟网络。我还创建了一个 Azure Connect 组，在其中添加了本地端点（On Premise DB）和 Windows azure 角色（测试控制器和测试代理）。当我在天蓝色上部署它时，我面临测试代理与测试控制器的连接问题。
测试控制器可以 ping 到我的本地数据库计算机，反之亦然。但我的测试控制器机器无法 ping 通云上的测试代理机器，反之亦然。
我已确保测试控制器上的以下内容
User testagent is part of group TeamTestAgentService
User testagent is also administrator on TestController hosted service.
Firewall exceptions have been added
如果我尝试 ping 两台天蓝色的计算机，我将无法做到这一点。默认情况下，azure 已禁用 ping，因此我添加了以下防火墙规则
netsh advfirewall 防火墙添加规则 name="ICMPv6" dir=in action=allow enable=yes protocol=icmpv6
但它仍然不起作用。我认为，如果这两台机器能够互相 ping 通，则测试代理与云上测试控制器的连接问题将得到解决。
I wanted to create a Test rig on cloud. I have created a windows azure hosted service that installs Test Controller and configures it with on premise DB. I have created another hosted service that installs Test Agent. I have enabled Virtual network in the Azure service by providing Activation token taken from azure portal. I also created a Azure Connect Group in which I added my local endpoint(On Premise DB) and windows azure roles( Test Controller rand Test Agent). When I deploy this on azure I am facing problem of Test Agent connectivity with Test Controller.
Test Controller can ping to my on premise DB machine and vice versa. But my test controller machine cannot ping test agent machine or vice versa on cloud.
I have ensured following things on test Controller
User testagent is part of group TeamTestAgentService
User testagent is also administrator on TestController hosted service.
Firewall exceptions have been added
If I try to ping two azure machines I cannot do that. By default azure has ping disabled so I added following firewall rule
netsh advfirewall firewall add rule name="ICMPv6" dir=in action=allow enable=yes protocol=icmpv6
but it still does not work. I think if these two machines will be able to ping each other the problem of test agent connectivity to test controller on cloud will be solved.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
来自 http://social.msdn.microsoft.com/profile/rlfh/ 的回复
它不会像你现在那样工作。控制器和代理必须处于不同的角色，而且您需要将 Azure Connect 安装为端点的控制器 - 不作为角色启用。因此，您想要手动配置控制器，然后它应该显示出来，以便您可以将其添加到“连接来源”列表中。让代理保持原样（azure connect 作为角色），然后它应该可以工作。连接到：部分中的角色将不允许相互通信，但端点可以 - 因为它们具有您选择允许此操作的选项。
当我从控制器计算机上的 azure 门户手动安装 Azure Connect 端点而不是将其启用为虚拟网络中的角色时，我的问题得到了解决。
Reply from http://social.msdn.microsoft.com/profile/rlfh/
It won’t work as you have it now. The controller and agents have to be in different roles, but also the controller you need to install Azure Connect as an endpoint– not enabled as a role. So, you want to configure the Controller manually, then it should show up so you can add it to the Connect From list. Leave the agents as they are(azure connect as a role) and then it should work. The Roles in the Connect TO: part won’t be allowed to intercommunicate, though an endpoint can – since they have the option you selected to allow this.
My problem was solved when I manually installed Azure Connect endpoint from azure portal on the controller machine instead of enabling it as a Role in Virtual network.