Hello,
In Network Policy Server (NPS), when you configure conditions in a network policy, you can specify multiple groups to allow or deny network access to users or computers. However, sometimes you may run into problems when configuring multiple groups, especially when you connect the conditions using "AND" logic. This is because NPS follows strict logic rules when evaluating policies.
If you add multiple groups to a network policy in NPS, and authentication fails, it may be because NPS is interpreting the conditions you set literally. For example, if you have the following conditions:
- The user belongs to group A.
- The user belongs to group B.
If the NPS policy is configured this way, only users who belong to both group A and group B will be authenticated. If the user belongs to only one of the groups, they will not meet the conditions, so NPS will deny authentication.
In order to add multiple groups and make authentication work, you need to make sure that the NPS policy correctly reflects your intent. Here are some possible solutions:
- If your goal is to allow users to authenticate as long as they belong to any of the groups, you need to make sure that the conditions in the policy are connected using "OR" logic. This may require creating multiple conditions or using different policies to cover all cases.
- Another approach is to create separate network policies for each group. Each policy has a condition that the user must belong to a specific group. You can then use priorities to determine which policy is adopted in case of conflict.
- Review the NPS log files and events in Windows Event Viewer for details on what NPS does when it processes authentication requests. This may provide clues as to why some users are denied access.
Best regards
Zunhui