Azure Web app connect to VM service on private network

0
votes

I've created windows server virtual machine with active directory controller and my web app is communicating with it on public ip successfully (by ldap), but when i try connect to ldap on private ip (virtual network) it does not respond

to my Web app i have set VNet Configuration ![enter image description here

my virtual machine network tab:

enter image description here

But it does not work when i try to connect to ldap://10.0.1.4:389

What should i do?

I can't even test my connection between webapp (by tcpping) and vm neither on public and private ip

i couldn't add to my webapp vnet integration on 10.0.1.0/24 because there was written that this subnet is already in use (or sth like that)

what should i type when i do vnet integration?

enter image description here enter image description here

2
azurenetworkingvirtualization

2 Answers

0
votes

VNet Integration with Azure web app is required a dedicated unused subnet for the network connection. The subnet should be a subnet where no other resources like Azure VM located.

Your configuration is correct. You could follow these troubleshooting steps to verify if the VNet integration is working well. You can test via port 3389 on Azure VM. In my case, there is not a DC deployed on Azure VM.

enter image description here

However, please note that

There are some things that VNet Integration doesn't support, like:

  • Mounting a drive.
  • Active Directory integration.
  • NetBIOS.

Thus, I suppose Idap does not work with VNet Integration.

0
votes

heh... i've created second virtual network, and integrated web app with it... next i have connected my second virtual network to first and... everything works great, ping's are < 1 ms... that's a bit embarassing that it did not work when both web app and virtual machine were in one virtual network and i don't know why