Share via

Wireless Connection Failed with Event 4625 and Failure Status Code 0xC000005E

Question

Monday, October 27, 2014 8:23 AM

My wireless infrastructure was working fine until recently, random occurrence of connection issues which are accompanied by Event 4625 with Failure Status of 0xC000005E in Event Log of the RADIUS server. The only way to resolve this now is to reboot my server hosting the Network Policy Server (RADIUS).

The following is my setup:

Domain controllers: Windows Server 2003 & Windows Server 2008 R2

NPS Server: Windows Server 2012

Enterprise Root Certificate Authority Server: Windows Server 2012

NPS Policies: > Network Policies: > 

NAS Port Type: Wireless - IEEE 802.11

Windows Group: MyDomain\Wireless-Guest Users

Authentication Type: EAP

I am using PEAP with MS-CHAP V2

The event log does not indicate very directly the root cause of my problem. I might have missed certain steps but I am not sure what. 

Any help or comment on this matter would be highly appreciated. 

Let me know if more details is required. The following is a copy of the event form the NPS server (with dummy names).

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          27/10/2014 3:35:25 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      Radiusserver.mydomain.com
Description:
An account failed to log on.

Subject:
Security ID: SYSTEM
Account Name: RadiusServer$
Account Domain: MYDOMAIN
Logon ID: 0x3E7

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: testuser1
Account Domain: MYDOMAIN

Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xC000005E
Sub Status: 0x0

Process Information:
Caller Process ID: 0x3f4
Caller Process Name: C:\Windows\System32\svchost.exe

Network Information:
Workstation Name:
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: CHAP
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.

  • Transited services indicate which intermediate services have participated in this logon request.
  • Package name indicates which sub-protocol was used among the NTLM protocols.
  • Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>4625</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-27T07:35:25.435758200Z" />
        <EventRecordID>853026</EventRecordID>
        <Correlation />
        <Execution ProcessID="736" ThreadID="216324" />
        <Channel>Security</Channel>
        <Computer>RadiusServer.mydomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-5-18</Data>
        <Data Name="SubjectUserName">RadiusServer$</Data>
        <Data Name="SubjectDomainName">MYDOMAIN</Data>
        <Data Name="SubjectLogonId">0x3e7</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">testuser1</Data>
        <Data Name="TargetDomainName">MYDOMAIN</Data>
        <Data Name="Status">0xc000005e</Data>
        <Data Name="FailureReason">%%2304</Data>
        <Data Name="SubStatus">0x0</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">CHAP</Data>
        <Data Name="AuthenticationPackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
        <Data Name="WorkstationName">
        </Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x3f4</Data>
        <Data Name="ProcessName">C:\Windows\System32\svchost.exe</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>
      </EventData>
    </Event>

All replies (3)

Tuesday, October 28, 2014 5:52 AM âś…Answered

Hi,

The status: 0XC000005E means there are currently no logon servers available to service the logon request. According to your description, the only way to resolve this problem is to restart the RADIUS, so some progress may be failed, or server(RADIUS) hang.

I suggest you to restart the service of Network Policy Server when this problem happens again:
1. Open Network Policy Server snap-in.
2. Right click NPS, and select Stop NPS Service.
3. After stopped, then select Start NPS Service to restart it.

Besides, install the newest update on the RADIUS. Check the event viewer and to see if there are some records relate to server hang.

Reference the link below for detailed information about troubleshooting server hangs:
http://blogs.technet.com/b/askperf/archive/2007/09/25/troubleshooting-server-hangs-part-one.aspx
http://blogs.technet.com/b/askperf/archive/2007/09/25/troubleshooting-server-hangs-part-two.aspx
http://blogs.technet.com/b/askperf/archive/2008/05/06/troubleshooting-server-hangs-part-three.aspx
http://blogs.technet.com/b/askperf/archive/2008/05/06/troubleshooting-server-hangs-part-four.aspx

Regards,           
Eve Wang

Wednesday, October 29, 2014 9:43 AM

Hi Eve,

Thanks for replying to my question. You suggested that I restart the NPS service when this issue happens again, which i did before I submit this post. It (restart NPS service) was effective only the first time when the issue happened, when the problem returns lately, restarting service is not effective -- I had to restart the whole server, which is bad.

You also suggested to install latest RADIUS update, I haven't tried that yet, and it could be due to a bug in NPS -- I am looking forward to install the update, however please advise how and where do obtain such update.

Meanwhile let me read the article you posted and subsequently check whether my server shows the symptom describe in the articles. I will update you again.

Thank you.

Tantl

Friday, October 31, 2014 7:04 AM

Hi Tantl,

The update which I mentioned was Windows Update,  install the latest update is the way to ensure a good performance for your device.

If there is any update about this issue, please feel free to connect me.

Best Regards,
Eve Wang