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
About bradcl_15
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About bradcl_15
07-17-2017
7Posts
0Likes
0Solutions
Jul 17, 2017Last Visited
User
Activity
User
Profile
Latest posts by bradcl_15
| Subject | Views | Posted |
|---|---|---|
| 3400 | 10-05-2015 05:24 PM | |
| 3774 | 10-01-2015 06:14 PM | |
| 2935 | 09-14-2015 07:27 PM | |
| 2951 | 09-14-2015 01:10 AM |
User Badges
Community Statistics
| Member Since | 05-12-2015 06:06 PM |
| Date Last Visited | 07-17-2017 09:47 PM |
| Posts | 7 |
10-05-2015
05:24 PM
Hi, The traffic seems to be heading to MS servers in the 64.4.0.0/18 range... which isn't outlined in that URL. I think this range is a MS Skype range. Cheers, Brad
... View more
10-01-2015
06:14 PM
Hi Guys, Recently we've configured Lync 2013 on our network. What i've noticed on the PA external firewall is the Lync federation traffic from the internal lync clients to for example 'Skype clients' on the web or other organizations is classified on the PA as 'unknown-tcp'... on port 443. Currently i've got a security policy purely allowing 'unknown-tcp' on port 443... but this isn't all that secure. Is there a workaround for this? or is this apart of lync that Palo Alto haven't developed an App-ID for yet? Cheers, Brad
... View more
Labels:
- Labels:
-
App-ID
-
Configuration
09-14-2015
07:27 PM
Great news. Glad to know someone else is trying to achieve the same as myself. I seem to have it working with business machines but not BYOD devices. Have you experienced any issues with iPad/Android devices and Captive Portal redirection? Can't seem to browse to the portal page from those devices.
... View more
09-14-2015
01:10 AM
Hi guys, I have a scenario whereby we have a publicly issued wildcard certificate for our organisation and I'm wanting to use this in conjunction with Captive Portal on the PA-500. I've set all policies up and configured Captive Portal to redirect to a Loopback interface on the firewall (through the use of a DNS name which resolves to the IP of the loopback). This wildcard certificate is mainly to allow BYOD devices to connect via the captive portal without certificate errors. - Is this possible though because I read that the Captive Portal 'Redirect' field needs to match EXACTLY what is configured as the CN in the certificate. - The wildcard certificate CN is *.blahblah.com and not the FQDN... I can't edit the certificates attributes (e.g. hostname/SAN fields) because its a public certificate. Thanks in advance. Brad
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-17-2017
09:47 PM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks