Trying to make Sentinel RMS Manager communicate through Azure Connect

Question

Here is my configuration: I have Sentinel RMS Server running on premise in my network (Sentinel RMS is the license management/rights management server). I have two physical machines, first one in the same domain as the RMS Server, and a second physical machine running in a completely different remote network. I also have one VM hosted in Azure. All the four computers are connected through Azure Connect. The RMS server supports IPV6. RMS Server listens on port 5093 UDP.

Execution Behavior: All four machines can successfully talk to each other through IPV6 - PING works. The two physical machines above can successfully communicate with the RMS server through Azure Connect (and checkout a license from it without trouble). The request originating from the VM hosted in Azure always fails. When I look at the network trace through WireShark, it appears that the communication does start from the Azure VM machine, but somehow it gets blocked in the Azure router. Anybody any insights on this?

 

Thanks, Sajan

Answer 1

Are you able to ping the RMS server from the VM hosted in Azure and vice versa?

---

Jason Chen, Windows Azure PM

Answer 2

Few things to check:

1. Name resolution from Azure hosted VM - that you can resolve the name of RMS server to Connect assigned IPv6 address

2. You can ping from Azure hosted VM to your RMS server

3. Ensure that required Firewall ports are open