Network Policy Server: No Domain Controller Available


  • When attempting to configure our domain controller as a Network Policy Server, I am receiving an error message stating that there is no domain controller available for domain K12.TX.US (which is the NETBIOS name of our domain).

    The Full DNS Name of our Domain is :

    Log Name:      System
    Source:        NPS
    Date:          3/7/2014 12:55:51 PM
    Event ID:      4402
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    There is no domain controller available for domain K12.TX.US.
    Event Xml:
    <Event xmlns="">
        <Provider Name="NPS" />
        <EventID Qualifiers="49152">4402</EventID>
        <TimeCreated SystemTime="2014-03-07T18:55:51.000000000Z" />
        <Security />

    Please help, as I believe that this is causing the following error:

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          3/7/2014 12:55:51 PM
    Event ID:      6273
    Task Category: Network Policy Server
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Network Policy Server denied access to a user.

    Contact the Network Policy Server administrator for more information.

    Security ID: NULL SID
    Account Name: abusby
    Account Domain: K12.TX.US
    Fully Qualified Account Name: K12.TX.US\abusby

    Client Machine:
    Security ID: NULL SID
    Account Name: -
    Fully Qualified Account Name: -
    OS-Version: -
    Called Station Identifier: 00-19-92-0C-E4-E9:NISD_Testing
    Calling Station Identifier: B8-E8-56-A8-D4-D9

    NAS IPv4 Address:
    NAS IPv6 Address: -
    NAS Identifier: -
    NAS Port-Type: Wireless - IEEE 802.11
    NAS Port: 0

    RADIUS Client:
    Client Friendly Name: Testing Access Point
    Client IP Address:

    Authentication Details:
    Connection Request Policy Name: BlueSocket Wireless Connections
    Network Policy Name: -
    Authentication Provider: Windows
    Authentication Server:
    Authentication Type: PEAP
    EAP Type: Microsoft: Secured password (EAP-MSCHAP v2)
    Account Session Identifier: -
    Logging Results: Accounting information was written to the local log file.
    Reason Code: 7
    Reason: The specified domain does not exist.

    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <TimeCreated SystemTime="2014-03-07T18:55:51.061488000Z" />
        <Correlation />
        <Execution ProcessID="584" ThreadID="4712" />
        <Security />
        <Data Name="SubjectUserSid">S-1-0-0</Data>
        <Data Name="SubjectUserName">abusby</Data>
        <Data Name="SubjectDomainName">K12.TX.US</Data>
        <Data Name="FullyQualifiedSubjectUserName">K12.TX.US\abusby</Data>
        <Data Name="SubjectMachineSID">S-1-0-0</Data>
        <Data Name="SubjectMachineName">-</Data>
        <Data Name="FullyQualifiedSubjectMachineName">-</Data>
        <Data Name="MachineInventory">-</Data>
        <Data Name="CalledStationID">00-19-92-0C-E4-E9:NISD_Testing</Data>
        <Data Name="CallingStationID">B8-E8-56-A8-D4-D9</Data>
        <Data Name="NASIPv4Address"></Data>
        <Data Name="NASIPv6Address">-</Data>
        <Data Name="NASIdentifier">-</Data>
        <Data Name="NASPortType">Wireless - IEEE 802.11</Data>
        <Data Name="NASPort">0</Data>
        <Data Name="ClientName">Testing Access Point</Data>
        <Data Name="ClientIPAddress"></Data>
        <Data Name="ProxyPolicyName">BlueSocket Wireless Connections</Data>
        <Data Name="NetworkPolicyName">-</Data>
        <Data Name="AuthenticationProvider">Windows</Data>
        <Data Name="AuthenticationServer"></Data>
        <Data Name="AuthenticationType">PEAP</Data>
        <Data Name="EAPType">Microsoft: Secured password (EAP-MSCHAP v2)</Data>
        <Data Name="AccountSessionIdentifier">-</Data>
        <Data Name="ReasonCode">7</Data>
        <Data Name="Reason">The specified domain does not exist.</Data>
        <Data Name="LoggingResult">Accounting information was written to the local log file.</Data>

    Friday, March 07, 2014 7:34 PM


All replies

  • Authentication from our m0n0wall BYOD firewall is working, but authentication from our 802.1x network is giving the "domain does not exist" error.
    Friday, March 07, 2014 7:36 PM
  • Hi,

    Thanks for your posting.

    Did you check this MS article?

    Event ID 4402 — NPS and Domain Controller Communication


    If you have any feedback on our support, please click here

    Vivian Wang

    Monday, March 10, 2014 10:25 AM
  • Hi,

    Any updates about the issue?

    Please feel free to let us know if you need further assistance.


    If you have any feedback on our support, please click here

    Vivian Wang

    Wednesday, March 12, 2014 5:46 AM
  • Yes I did see that article, and there are plenty of logs from another device that authenticates via RADIUS. Requests from our 802.1x wireless network are giving the "the specified domain does not exist" error. I can enter the username asusername, username@domain, or domain\username and neither method fixes the error.
    Monday, March 24, 2014 3:52 PM