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 Parkkapyong
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About Parkkapyong
07-11-2022
1Post
0Likes
0Solutions
Jul 11, 2022Last Visited
User
Activity
User
Profile
Latest posts by Parkkapyong
| Subject | Views | Posted |
|---|---|---|
| 8851 | 04-13-2022 10:52 PM |
User Badges
Community Statistics
| Member Since | 07-01-2021 11:03 PM |
| Date Last Visited | 07-11-2022 11:42 PM |
| Posts | 1 |
04-13-2022
10:52 PM
I experienced the same issue. It was connected normally after two actions. # First Action The firewall's DNS IP settings were set differently than the Kerberos (AD) server IP to work with. --> The firewall's DNS IP setting has been changed to Kerberos (AD) server IP. Packets collected by the firewall. Check the SNameString value of the TGS-REQ packet. # Second action You have added permissions to the AD server so that you can use AES 128, AES 256 in the firewall AD account option. # Firewall PAN-OS: 9.1.12 # AD (kerveros) server: Windows Server 2016 # Link to how to set up Winrm-http https://docs.paloaltonetworks.com/pan-os/9-0/pan-os-admin/user-id/map-ip-addresses-to-users/configure-server-monitoring-using-winrm
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-11-2022
11:42 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks