Palo Alto Networks Knowledgebase: How Can IP Overlaps be Prevented with GlobalProtect
How Can IP Overlaps be Prevented with GlobalProtect
Created On 09/25/18 17:39 PM - Last Updated 08/05/19 20:36 PM
When a remote user connects to the corporate network with GlobalProtect, the computer will be assigned an IP address from the pool configured on the gateway. It is possible that this IP address overlaps the subnet that the workstation is already in, which will cause issues.
For example: A remote employee is connecting from a hotel room where the IP address received locally was in the 10.0.0.0/8 range. The IP pool available for GlobalProtect clients is 10.1.1.0/24. This will cause issues since the IP pool is part of the local subnet.
In this case, the following error is generated in System logs on the firewall: "Assign Private IP address failed".
The recommended solution for this issue is to create a new IP pool in a different subnet and leave that new pool lower on the list. IP pools are used from the top down, but if the client is in a subnet that conflicts with the first IP pool, the firewall will assign an IP address from the second pool automatically.