Apology for asking multiple question for the past one week..
We've define a policy to allow active-directory-base application which includes most of the AD standard ports, but the traffic is not hitting the policy, eventhough the destination ports are a match. Any reason why ?
As a workaround for now, we added new custom service for the policy and it worked, but still puzzled why it's not hitting the policy above.
The reason probably is that this one application simply isn't enough. When you look at the application information, you will see thst there are other apps which active-directory-base depends on. What application did you see in the logs which was not allowed?
If you try to allow domain communication from domain joined clients/servers, please take a look at this post: https://live.paloaltonetworks.com/t5/general-topics/allow-workstations-to-join-domain-controller/m-p...
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!