I have set up a worker role that starts a native application running in the cloud that listens on an internal endpoint on port 9900. I have also setup Azure connect according to Microsofts instructions. I can ping the worker role instance using the IPV6 address obtained from the management portal. I can also connect to it from a webrole, however I cannot connect to it from my local machine using Azure connect. Every time I try this the connection attempt timesout. Should it be possible to connect to an internal endpoint using connect? All the examples I have seen connect from a role in the cloud back to a local machine not the other way round, but I cannot find anything that says that this is not possible.
2 Answers
1
votes
The above information is not enough to tell what is wrong or why you can not connect to your worker role from a local on-premise machine. Once Azure connect is installed and configured n both Azure Role and Local Machine, you can connect from both sides. Even when Azure connect do not have any updates in last 2 years, you still can use this preview/beta feature.
What you can do is run some troubleshooting test as described below and then provide some troubleshoting logs back here to provide accurate help.
Also if possible re-check your Azure connect configuration using this info: Checklist for Configuring Connections for Windows Azure Roles
Once side node, if you can use Windows Azure Virtual Networks, that is best rather then using Azure Connect. Here is the link which can help:
0
votes
I finally worked this out. The worker role endpoint has to be created as input not internal even though it is not meant to be publicly accessable. The Azure connect VPN then blocks all input apart from the computers added to the relevant group. This was not at all clear from the documentation. I tested it from another computer not added to the group and it was blocked, so the VPN is working.
