Partager via

Event ID 6275 — NPS Accounting Message Processing

  • Article

Applies To: Windows Server 2008

Network Policy Server (NPS) processes accounting request messages that it receives from configured RADIUS clients.

Event Details

Product: Windows Operating System
ID: 6275
Source: Microsoft-Windows-Security-Auditing
Version: 6.0
Symbolic Name: SE_AUDITID_ETW_NPS_ACCT_RESPONSE_DISCARD
Message: Network Policy Server discarded the accounting request for a user.

Contact the Network Policy Server administrator for more information.

User:
%tSecurity ID:%t%t%t%1
%tAccount Name:%t%t%t%2
%tAccount Domain:%t%t%t%3
%tFully Qualified Account Name:%t%4

Client Machine:
%tSecurity ID:%t%t%t%5
%tAccount Name:%t%t%t%6
%tFully Qualified Account Name:%t%7
%tOS-Version:%t%t%t%8
%tCalled Station Identifier:%t%t%9
%tCalling Station Identifier:%t%t%10

NAS:
%tNAS IPv4 Address:%t%t%11
%tNAS IPv6 Address:%t%t%12
%tNAS Identifier:%t%t%t%13
%tNAS Port-Type:%t%t%t%14
%tNAS Port:%t%t%t%15

RADIUS Client:
%tClient Friendly Name:%t%t%16
%tClient IP Address:%t%t%t%17

Authentication Details:
%tProxy Policy Name:%t%t%18
%tNetwork Policy Name:%t%t%19
%tAuthentication Provider:%t%t%20
%tAuthentication Server:%t%t%21
%tAuthentication Type:%t%t%22
%tEAP Type:%t%t%t%23
%tAccount Session Identifier:%t%t%24
%tReason Code:%t%t%t%25
%tReason:%t%t%t%t%26

Resolve

Correct the cause of the discarding of Accounting-Request messages

To perform this procedure, you must be a member of Domain Admins.

To correct the cause of the discarding of Accounting-Request messages:

  1. Network corruption, latency, or other network problems unrelated to NPS might produce this condition. Wait a short while to see if the condition still exists. The problem might resolve itself.
  2. Make sure that the RADIUS client configuration, including the IP address of the RADIUS client and the shared secret configured on the server running NPS and on the RADIUS client, is correct. To configure a RADIUS client:
    1. Click Start, Administrative Tools, Network Policy Server. The NPS Microsoft Management Console (MMC) opens.
    2. Double-click RADIUS Clients and Servers.
    3. Click RADIUS Clients, and in the details pane, right-click the RADIUS client that you want to configure.
    4. Click Properties, and then change the configuration according to your requirements.
  3. Make sure that the network access server is configured with the IP address of the server running NPS.
  4. If you are using SQL Server logging, check the connection between the SQL Server database and the server running NPS. Confirm that the SQL Server database is online and working. To check the SQL Server connection in NPS:
    1. Click Start, Administrative Tools, Network Policy Server. The NPS MMC opens.
    2. In the console tree, click Accounting.
    3. In the details pane, click Configure SQL Server Logging.
    4. In SQL Server Logging, click Data Source.
    5. In Data Link Properties, click Test Connection.
  5. If these actions do not resolve the problem, restart the NPS service. To restart the NPS service:
    1. Click Start, Administrative Tools, Network Policy Server. The NPS MMC opens.
    2. From the Action menu, click Stop NPS Service.
    3. From the Action menu, click Start NPS Service.
  6. If restarting the NPS service does not resolve the problem, restart the network access server.
  7. If restarting the network access server does not resolve the problem, restart the server running NPS.

Verify

To perform this procedure, you must be a member of Domain Admins.

To verify that Accounting-Request messages are being logged:

  1. Confirm the network access server is configured to send accounting requests to the server running NPS.
  2. Attempt to connect to the network through the network access server with an access client.
  3. Examine the accounting log or SQL Server database to confirm that accounting records are being logged by NPS. The default log file location is %Systemroot%Windows\system32\LogFiles.

NPS Accounting Message Processing

Network Policy Server Infrastructure