When a user attempts to connect through 802.1x running on IAS, they cannot connect. IAS eventlog reports event ID 2, Reason Code = 65, permission for the user account was denied.
Once user has been confirmed to be member of proper AD group with permission in IAS' Remote Access Policies (RAP), check user's AD account to confirm their "Dial-In" setting to be "Control access through Remote Access Policy".
Subscribe to:
Post Comments (Atom)
1 comment:
HI I HAVE ALMOST THE SAME PROBLEM
FIRST BEFORE STARTING 802.1X AUTHENTICATION USERS COULD HAVE REMOTE DESKTOP CONNECTION BETWEEN TWO HOST IN THE NETWORK
JUST AFTER ENABLING 802.1X AUTHENTICATION
THE USERS COULD EFFECTIVELY HAVE AN AUTHORIZED ACCESS TO THE NETWORK ?BUT WHEN WE WANT TO REMOTLLY CONNETCT TO THAT USER WITH REMOTE DESKTOP CONNECTION THE USER GO TO RESTRICTED AREA AND REMOTE CONNECTION BLOCKS ALSO I GET AN EVENT IN MY EVENTS LOG WITH THE REASON ID NUMBER 65
"he connection attempt failed because network access permission for the user account was denied. To allow network access, enable network access permission for the user account, or, if the user account specifies that access is controlled through the matching network policy, enable network access permission for that network policy"
Post a Comment