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 tkenning
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About tkenning
01-23-2019
4Posts
0Likes
0Solutions
Jan 23, 2019Last Visited
User
Activity
User
Profile
Latest posts by tkenning
| Subject | Views | Posted |
|---|---|---|
| 1969 | 09-18-2012 11:58 PM | |
| 2771 | 09-18-2012 11:42 PM | |
| 2771 | 09-18-2012 11:15 PM | |
| 1868 | 12-09-2011 09:07 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 7 Likes |
User Badges
Community Statistics
| Member Since | 12-06-2011 03:51 AM |
| Date Last Visited | 01-23-2019 01:53 PM |
| Posts | 4 |
09-18-2012
11:58 PM
Heard about the IP change of the update servers, but ignored it. We've been using updates.paloaltonetworks.com in our PAs in the past as well as today. If I had faced update problems, I would have spend some time on hardcoding update IPs. P.S.: I don't see 329-1511 in Panorama at all, too. As mentioned before.
... View more
09-18-2012
11:42 PM
09-18-2012
11:15 PM
Hi everybody, when looking into the dynamic updates section via https://support.paloaltonetworks.com I do not see update 329, yet. 328 is the latest named one. In Panorama I do not see availability of 329 as well. The PA's itself have already updated to 329-1511! Looking into the release news (direct link using webGUI): https://updates.paloaltonetworks.com/updates/ReleaseNotes.aspx?type=si&versionNumber=329-1511&content=contents&inc=False https://updates.paloaltonetworks.com/updates/ReleaseNotes.aspx?type=si&versionNumber=329-1511&content=apps&inc=False Default-action 35017: reset-client Default-action 35018: alert
... View more
12-09-2011
09:07 AM
Hello everybody, we are running the latest PAN-OS 4.1.0 and Panorama in an evaluation environment and would like to deploy Client-VPN the following way: We do run our own CA in our Corporate network. We use our own PKI infrastructure and Aladdon eToken with client certificates on it for Client-VPN throgh MS ISA since years. Users do not know their MS AD-User account passwords, they do know their PIN for the PKI eToken only. We do not use Single-Sign-On. We do have our own Radius server (IAS). Problem: --------------- Connecting via client-vpn using (AD) user and password is not an option (s. above). Question(s): --------------- PaloAlto only supports PAP, but no EAP for certificates. True? To replace our ww infrastructure of MS ISA f. client-vpn, we need to logon using certificates on our clients and (if possible) PIN of PKI client. Is there any way to manage this? tkenning
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
01-23-2019
01:53 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks