About Brett-Welch

OtakarKlier · ‎01-21-2022

Hello, Take a look at the logs and see where the traffic is getting blocked. If the DHCP server is not on the same vlan, the layer 3 interface on the vlan will be the one responsible for the dhcp relay. Regards,

Brett-Welch · ‎04-07-2021

So that was a partial solution to the problem. I didn't realize that there had been some static routes that had been set to point to the 5250s where this was previously set up. I adjusted the static routes to point to the new 3220s and I am now able to ping the internal DNS and do NS Lookups via the internal DNS but cannot resolve over http to internal sites it seems and when I set a static on the VPN adapter, I can no longer ping the internal DNS or do nslookups.

BPry · ‎08-31-2020

@Brett-Welch, When you say recently, how recently is recently? When you modify the agent configuration it can take quite a bit of time for all of the agents to pull the new configuration depending on how you have things (refresh-config-interval) setup. Until they actually pull the new agent configuration the welcome page will still be served.

Member Since	‎03-27-2020 11:13 AM
Date Last Visited	‎01-28-2022 02:01 PM
Posts	4

Online Status	Offline
Date Last Visited	‎01-28-2022 02:01 PM

About Brett-Welch

Configuring PA-5250 to act as gateway for guest wireless

Re: Global Protect Client IP Range not able to get to internal resources

Global Protect Client IP Range not able to get to internal resources

GlobalProtect VPN Client Welcome Page

Re: Configuring PA-5250 to act as gateway for guest wireless

Re: Global Protect Client IP Range not able to get to internal resources

Re: GlobalProtect VPN Client Welcome Page