Event 6273 with reason code 49 — "The connection request did not match any configured connection request policy." Connection request policies are evaluated before network policies; when none matches, the request is dropped immediately. This is usually a conditions problem on the CRP itself (day/time restrictions, NAS type conditions) or a deleted/disabled default policy.
Reason code 49
NPS 6273 reason 49: no matching connection request policy
What it means
Common causes
The default connection request policy ('Use Windows authentication for all users') was deleted or disabled without a replacement covering these requests.
CRP conditions (NAS Port Type, Client Friendly Name, day and time restrictions) exclude the request.
Requests intended for forwarding to a remote RADIUS group hit a CRP whose conditions no longer match after a NAS change.
How to fix it
In NPS console > Policies > Connection Request Policies, confirm at least one enabled policy matches these requests; the simplest healthy state is the default policy with Day and time restrictions covering 24x7.
Compare the event's NAS Port Type and Client Friendly Name against each CRP's conditions.
If you use RADIUS proxying, verify the CRP that forwards to the remote RADIUS server group still matches the NAS names/IPs after infrastructure changes.