Event ID 18 — NPS Server Communication
Updated: December 16, 2008
Applies To: Windows Server 2008 R2
Network Policy Server (NPS) must be able to communicate with configured RADIUS clients in order to receive and process connection requests.
|Product:||Windows Operating System|
|Message:||An Access-Request message was received from RADIUS client %1 with a message authenticator attribute that is not valid.|
Fix the cause of the malformed RADIUS message
This condition can occur if the server running NPS receives one of the following from a RADIUS client:
- A response that is a malformed message.
- A response that contains an incorrect value in the Code field.
- An Access-Request message that does not contain a Message-Authenticator attribute.
- A response that contains a message authenticator that is not valid.
- An Access-Request message that contains an Extensible Authentication Protocol (EAP) message, but no Message-Authenticator attribute.
- A response with an attribute that exceeds the maximum RADIUS attribute length.
To perform this procedure, you must be a member of Domain Admins.
To fix the cause of the malformed RADIUS message:
- Network corruption, latency, or other network problems unrelated to NPS might produce this condition. Wait a short while to confirm that the condition still exists. The problem might resolve itself.
- Make sure that the remote RADIUS server configuration, including the IP address of the RADIUS client/proxy server and the shared secret configured on the server running NPS and on the RADIUS client, is accurate. To configure a RADIUS client:
- Click Start, Administrative Tools, Network Policy Server. The NPS Microsoft Management Console (MMC) opens.
- Double-click RADIUS Clients and Servers.
- Click RADIUS Clients, and in the details pane, right-click the RADIUS client you want to configure.
- Click Properties, and then change the configuration according to your requirements.
- Make sure that the network access server is configured with the IP address of the server running NPS.
- If these actions do not resolve the problem, contact the RADIUS server vendor to see if the remote RADIUS server complies with the RADIUS protocol specification.
To verify that RADIUS messages are not malformed:
- On the server running NPS, start an application that is used to capture network traffic and begin a capture.
- On a computer that is configured according to network access policy to connect to the network, log on to the network with a valid user account and valid credentials through the RADIUS client that previously sent the malformed message.
- On the server running NPS, stop the network traffic capture, and then confirm that the structure of the messages presented to the RADIUS server by the RADIUS client is correct.