06-03-2020 10:45 AM - edited 06-03-2020 10:46 AM
Hello Folks.
So we have configured GP in one VM-Series in a Cloud Community. We are experiencing unusual behavior. I do not know whether it was the GP configuration or it is in the VM. So sample VM 1 has an IP of 192.168.14.X and VM 2 has an IP of 192.168.14.X when connected in GP I can ping VM1 also the traceroute is complete but when trying to reach VM 2 is shows RTO and it is not reachable via traceroute. When looking into the firewall logs it show that the the traceroute is allowed going to VM 2 with an application of traceroute, also it hits the right rule.
Thank you for your answers if you replied.!
06-11-2020 12:19 AM
Found the problem here. Never assign any network for GP that has the same segment as an interface of a vm that is behind the firewall.
06-03-2020 07:20 PM - edited 06-03-2020 07:21 PM
Does the other VM have a route back to whatever IP space you are using for GlobalProtect clients? If you take a packet capture on the unreachable VM does it show traffic hitting the VM from GlobalProtect clients?
06-03-2020 11:36 PM
Yep, just took PCAP just now the GP reaches the ping but the server does not response back.
06-11-2020 12:19 AM
Found the problem here. Never assign any network for GP that has the same segment as an interface of a vm that is behind the firewall.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
