This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Brett-Welch
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About Brett-Welch
01-28-2022
4Posts
0Likes
0Solutions
Jan 28, 2022Last Visited
User
Activity
User
Profile
Latest posts by Brett-Welch
| Subject | Views | Posted |
|---|---|---|
| 564 | 01-20-2022 03:06 PM | |
| 837 | 04-07-2021 02:55 PM | |
| 880 | 04-07-2021 01:29 PM | |
| 689 | 08-31-2020 04:30 PM |
User Badges
Community Statistics
| Member Since | 03-27-2020 11:13 AM |
| Date Last Visited | 01-28-2022 02:01 PM |
| Posts | 4 |
01-20-2022
03:06 PM
Hi All, I'm attempting to configure a 5250 to act as the gateway and DHCP server for my guest wireless. I have a Cisco 9800 WLC directly connected via fiber from Gi0/2 to Eth1/15 on the 5250 over VLAN 825. I then created VLAN 825 on the 5250 as an SVI and associated it with Eth1/15. I have a DHCP server setup to hand out IPs from the 10.14.0.0/19 subnet. My APs are communicating fine via my internal coporate network however I can't seem to get an IP address from the FW. I also can't set a DNS server to be handed out via DHCP. Eth1/15 is currently a layer 2 port. I'm wondering if I need to make Eth1/15 a layer 3 port and move the gateway from the VLAN 825 interface to Eth1/15.
... View more
04-07-2021
02:55 PM
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.
... View more
04-07-2021
01:29 PM
Hi All, I recently configured an HA pair of 3220s for Global Protect. I have the firewalls handing out IPs from the 192.168.124.0/22 network. The clients can connect and get the correct IPs but are not able to reach internal resources. This same IP range had been setup on a pair of 5250s and I believe I had everything setup for this to work on the new 3220s but for some reason it is not working. I can see that the 3220s have routes for everything on our network and can reach them as well as the outside world. I'm not sure what else to check on the Global Protect gateway. Any ideas?
... View more
08-31-2020
04:30 PM
Hello, We had the welcome page for GlobalProtect VPN Client enabled at one point. We recently disabled it but the welcome page still displays upon connect. Has anyone else run into this and found a way to permanently turn off the welcome page?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
01-28-2022
02:01 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks