Hi,
in my company we have some VMs in the same Virtual Network within the same Subnet. In windows explorer of a VM we are not able to see other VMs in Network Resource panel. There is a reason why there is such a behaviour?
Thanks,
Alessandro
NETBIOS Protocol does not work across different subnets
In Azure-provided name resolution WINS and NetBIOS are not supported. You cannot see your VMs in Windows Explorer.
-Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.
Thanks.
We have a proprietary application that use COM+ and we need to put in communication an Azure Windows Virtual Desktop (COM+ Proxies) with an application server on our on-premises LAN where the COM+ Services are.
We have also already done the tests with DTCPing and passed successfully.
What we have to do in order to use COM+ services on multiple VMs in two different VNETs?
I think if you follow the below steps, you should be able to enable communication between these services on multiple VMs/VNets.
Turn on Network Access,
Add an exception in Windows Firewall rules
Open RPC port on NSGs on both machines
For traffic between Vnets, make sure they are connected and the vnets can talk to each other.
I hope this helps. Please let us know if you require any further assistance and we will be glad to assist further. Thank you!
Remember:
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.
Want a reminder to come back and check responses? Here is how to subscribe to a notification.
5 people are following this question.
