Wireless AP not logging on

I have a wireless network with multiple APs controlled by my firewall.
I've setup a radius server and the firewall authenticates back to the radius server for the wifi network.
All of a sudden, it just stopped working.  So far, every laptop I tried to connect fails. I get the error message say "windows was unable to connect to the OFFICEAP"   OFFICEAP is my SSID.

I have attached 2 screenshots.
12
Here's what I've done so far:
1. I've restarted the following services on my DC, where the radius server is on.
 network policy server service
IKE and AuthIP IP sec keying modules service
AD certificate services service

2. On the clients, I've ran the following commands:
     netsh winsock reset
     disabled and enabled NIC
     removed the saved network

3.  I've restarted one of the APs

4.  I've tested 4 different laptops, with win xp and wind 7, and they all don't work.


Any idea's what I can try next?
DanNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Logs logs and logs! If your firewall is also your AP controller, I guarantee you can see a log with RADIUS requests and results.

NPS also logs all radius traffic and will tell you in the event log why it decided to allow, or deny, a request. Normal windows application events there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bleeuwenCommented:
Just like the error said, it is a problem with the network authtication. A user can not authenticate. Like Cliff said it start with checking the logs. It could be something simple like an expired password, but you should find something in the logs.
0
DanNetwork EngineerAuthor Commented:
Where are the radius logs?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

bleeuwenCommented:
I've setup a radius server

I think you know best? Which application are you using?
0
DanNetwork EngineerAuthor Commented:
just the built in network policy server from Microsoft.
I've looked through the windows logs, but I can't find out specifically to the radius authentication, I guess I need to continue googling :)
0
DanNetwork EngineerAuthor Commented:
Not sure sure if this has anything to do with it, but how can my DC be locked?

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          3/11/2015 8:56:21 AM
Event ID:      4625
Task Category: Account Lockout
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      dc1.domain.org
Description:
An account failed to log on.

Subject:
      Security ID:            SYSTEM
      Account Name:            DC1$
      Account Domain:            domain
      Logon ID:            0x3E7

Logon Type:                  3

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            info
      Account Domain:            domain

Failure Information:
      Failure Reason:            Account locked out.
      Status:                  0xC0000234
      Sub Status:            0x0

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

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

Detailed Authentication Information:
      Logon Process:            IAS
      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>12546</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-11T15:56:21.650756000Z" />
    <EventRecordID>132912409</EventRecordID>
    <Correlation />
    <Execution ProcessID="508" ThreadID="4944" />
    <Channel>Security</Channel>
    <Computer>dc1.domain.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">DC1$</Data>
    <Data Name="SubjectDomainName">domain</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">info</Data>
    <Data Name="TargetDomainName">domain</Data>
    <Data Name="Status">0xc0000234</Data>
    <Data Name="FailureReason">%%2307</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">IAS</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">0x354</Data>
    <Data Name="ProcessName">C:\Windows\System32\svchost.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
  </EventData>
</Event>
0
DanNetwork EngineerAuthor Commented:
whats strange is, I tried a couple of iPhones, and they connect just fine to my OFFICEAP SSID.
when I try any laptop, it doesn't connect.

I'm baffled.
0
DanNetwork EngineerAuthor Commented:
thanks guys for your input at least.

I made some changes to the NPS, and then pushed the changes via AD to the windows clients.

That seemed to do the trick.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Networking

From novice to tech pro — start learning today.