it could be that the client still connected, to confirm remove the connection entry in the Azure VPN client and re-import the XML file and try to reconnect. I hope that helps.
Hi i hope that you will notice me, my current setup is this. I have my main office connected to my domain controller in Azure via site to site vpb. Next is i want to jpin my workstations outside my head office via point to site vpn. Can i update the group policy of my users that are joined via point to site vpn or they will just use the cached credentials during their login because they are logged on first before connecting to vpn
Thanks for watching my channel, in this case since you will be using a P2S (point to Site) they users will use cached credentials until the VPN tunnel is created.
Great explanation! Quick question, can you do the same DNS steps but with radius authentication?
Good content
thank you !!
Great video anyone? Y when our users connect to azure VPN it connects to AD sites instead of Azure DC?
Thanks for the video, after adding the custom DNS and trying to connect to the VPN again I got Exception during connect: The object already exists.
it could be that the client still connected, to confirm remove the connection entry in the Azure VPN client and re-import the XML file and try to reconnect. I hope that helps.
Hi i hope that you will notice me, my current setup is this. I have my main office connected to my domain controller in Azure via site to site vpb. Next is i want to jpin my workstations outside my head office via point to site vpn. Can i update the group policy of my users that are joined via point to site vpn or they will just use the cached credentials during their login because they are logged on first before connecting to vpn
Thanks for watching my channel, in this case since you will be using a P2S (point to Site) they users will use cached credentials until the VPN tunnel is created.