I would like to connect to Global protect on my azure virtual machine. installation is not an issue. but when I connect to VPN, I get disconnected from VM and when connection comes back global protect is no longer connected.
Can anyone help ?
I'm running into the same problem but only when I use the Azure VPN P2S Gateway. I have other VMs in Azure that do not use the Azure VPN GW and I don't encounter any issues using Global Protect.
I found this article detailing why it's happening and some workarounds. The "Nested Remote Desktop Connection" option worked for me though it's not ideal. I'm reading through the "Configure a Source NAT on the Router" option and trying to figure out how to apply it using the Azure VPN GW.
https://knowledgebase.paloaltonetworks.com/kCSArticleDetail?id=kA14u000000HAoM
Related
I am trying to rdp from my local mac to an Azure instance through a (IKEv2) vpn connection. I am never prompted for a password, and it looks like the connection just times out. The error code I get is 0x204.
I have tried using both Microsoft Remote Desktop 8 and 10 for mac.
The connection is active and reports that it is connected.
From the mac, I can connect to another VM (in the same azure account) which is not running behind a vpn.
From Parallels Desktop (with networking set to Shared mode and the vpn connection active on the mac), I can successfully connect using the windows rdp client.
So it seems the Microsoft RDP-client for mac is not using the vpn connection.
Is there a way to make it do so?
Is there another solution, that will allow me to rdp to an Azure VM from my mac (without going through Parallels)?
Note: This is not the same question as this, since that is not about going through an azure vnet gateway.
I needed to add hosts file entries for each azure site I needed to access.
For example for accessing my-vm-name.someregion.cloudapp.azure.com, I needed to add a hosts file entry for it's private IP within the subnet. E.g. 10.2.0.100.
The reason everything worked in Windows under Parallels, is that the relevant entries had already been added to the hosts file previously.
I am unable to access all of the resources in my peered network in Azure when I do a VPN from macbook (VPN type IKEV2) have tried add routes didn't worked.
In windows to get this working was to edit the routes.txt file and add static routes in.
How will I go adding the same in Mac.
System Details
Mac osx - 10.13.2
Looking for
Ability to add/define static routes for my peered virtual network for IKEV2 type VPN in mac.
We found a bug in the P2S VPN gateway that prevent this from working out of the box. The fix is currently being rolled out in Azure. You can wait until next week when we complete the rollout, or open a Service Request from Azure Portal and our support engineer can apply the fix directly to your Azure Gateway. Sorry for the issue you are running into.
Thanks,
Yushun [MSFT]
i create a win2012r2 datacenter vm on azure. i'm trying to connect via RDC but rdc cannot connect. i use the rdp file that azure provide, and also tryied to do it by myself manually in rdc (dns:port and also ip:port) but still i can't connect. how to check where the problem is?
Thanks
Are you in a Crop. network? I means did you check the firewall settings on your side? And kindly reminder, the default RDC port is NOT 3389.
this is the first time I am trying to host at Iaas level using microsoft azure. I have created a VM, microsoft server 2012. But I cannot access the VM using the DNS name.
Based on the content of the comments, I see three things that could be wrong
1) Apache is not listening on the external IP of the VM
2) Firewall is not configured to allow for access
3) Since you mentioned DNS, is that the *.cloudapp.net hostname or a custom DNS? If it's the latter, maybe it isn't distributed yet or misconfigured?
Which of these did you check already? Then we can guide you through the remaining ones.
Actually the question is kind of duplication of the following one Unable to access a locally hosted wcf service over the internet but with only difference that the service is hosted by a windows service on Azure Virtual Machine.
I can access the service on the machine and I have added an endpoint to the service port at Azure Configuration console, but still cannot access the service over the Internet.
The error message that is not possible to set up connection.
Is my scenario technical possible on azure? if yes - what is done wrong?
The answer to my question was pretty straightforward. Although I opened my endpoint in Azure Management Console the port was blocked by the virtual machine firewall (windows firewall). After setting in- and out- tcp port rule, the problem had gone.