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 MaximAvtonenko
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About MaximAvtonenko
11-09-2018
5Posts
3Likes
0Solutions
Nov 09, 2018Last Visited
User
Activity
User
Profile
Latest posts by MaximAvtonenko
| Subject | Views | Posted |
|---|---|---|
| 5550 | 07-11-2018 01:32 AM | |
| 6820 | 03-20-2017 12:07 AM | |
| 6888 | 03-17-2017 05:44 AM | |
| 6791 | 06-20-2016 04:50 AM | |
| 6820 | 06-18-2016 11:01 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 07-11-2018 01:32 AM | |
| 1 Like | 03-17-2017 05:44 AM | |
| 1 Like | 03-20-2017 12:07 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like |
User Badges
Community Statistics
| Member Since | 01-18-2016 01:16 AM |
| Date Last Visited | 11-09-2018 10:06 AM |
| Posts | 5 |
| Total Likes Received | 3 |
07-11-2018
01:32 AM
1 Kudo
https://live.paloaltonetworks.com/t5/Management-Articles/GlobalProtect-Requests-System-Keychain-Access-on-Mac-OS-X/ta-p/53332 Issue Machine Certificate authentication is used on MAC OS X clients. During the GlobalProtect connection process, the user needs to enter the Local Administrator account credentials to allow access to the System keychain twice. Cause When using Machine Certificates with GlobalProtect on Mac OS X Clients, the certificate must be accessed from the "System" keychain in MAC OS X. This will cause a Keychain Access prompt to appear twice when the client attempts to access the certificate for verification against both portal and gateway. Workaround Open the Keychain Access application and locate the Machine Certificate issued to Mac OS X Client in the System keychain. Right-click on the private key associated with Certificate and click Get Info, then go to the Access Control tab Click '+' to select an Application to allow Press key combination <Command> + <Shift> + G to open Go to Folder Enter '/Applications/GlobalProtect.app/Contents/Resources' and click Go Find PanGPS and click it, and then press Add Save Changes to private key PS: our MAC begin connecting only after all apps access were given to the key file. The steps above allows GlobalProtect access to only THIS certificate and private key. It will no longer prompt for keychain access, giving users a seamless, no-touch experience with Palo Alto Networks GlobalProtect. Note: The procedure has to be done again every time client is updated. https://live.paloaltonetworks.com/t5/Configuration-Articles/macOS-X-10-13-amp-iOS-11-New-Requirements-for-GlobalProtect/ta-p/179049
... View more
03-20-2017
12:07 AM
1 Kudo
When you allowing applications you have ssl and web-wrowsing for users anywhere. If policy needs to deny this access you must use URL filtering...
... View more
03-17-2017
05:44 AM
1 Kudo
To allow skype you need to allow next applications in security rule: Next step you need to make URL filtering profile. Deny any categories. But allow next URLs: mobile.pipe.aria.microsoft.com *.microsoft.com *.skype.com ocsp.msocsp.com login.live.com auth.gfx.ms *.skypeassets.com skype-m.hotmail.com *.messenger.live.com I hope it will usefull.
... View more
06-20-2016
04:50 AM
The problem because of NetBIOS probes have queue
When we disable NetBIOS probes all users have no access after relogon.
Than we enable WMI probes the problem of User-ID disapear for correct user rights for WMI probes we use: wmic /node:(IP address) computersystem get username
The installation is about 1500 users and 2 User agents.
... View more
06-18-2016
11:01 AM
Users have no access.
[Debug 988]: Reached max allowble probes, adding IP 10.100.xxx.xxx to queue for later processing. Probing 40 IPs, list contains 117 entries Reached max allowble probes, adding IP 10.100.xxx.xxx to queue for later processing. Probing 40 IPs, list contains 117 entries Probing IP 10.100.xxx.xxx failed. For initial probing, try again after 3 min [ Info 938]: IP 10.100.xxx.xxx is already in the probing queue
[Debug 484]: IP 10.100.xxx.xxx for acme\user cannot be probed. List is full of 201 entries, currently probing 40
+0500 Error: pan_user_id_agent_proc_ipuser(pan_user_id_uia.c:444): pan_user_id_agent_send_ip_user_to_dp() failed for user acme\user
+0500 Error: pan_user_id_uia_handle_ip_msg_i(pan_user_id_uia_v5.c:141): pan_user_id_agent_proc_ipuser(vsys 1, ip 10.100.xxx.xxx, user acme\user, timestamp 1466142528) failed
What we can do?
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks