Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 9/24/2015 2:35:32 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: USA\rename_guest
  Account Name: 
  Account Domain: USA
  Fully Qualified Account Name: USA\rename_guest

Client Machine:
  Security ID: NULL SID
  Account Name: -
  Fully Qualified Account Name: -
  OS-Version: -
  Called Station Identifier: 0A-27-22-F3-BF-98:iHeart
  Calling Station Identifier: A0-39-F7-21-4D-B8

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

RADIUS Client:
  Client Friendly Name: router-2
  Client IP Address:

Authentication Details:
  Connection Request Policy Name: Secure Wireless Connections
  Network Policy Name: -
  Authentication Provider: Windows
  Authentication Server:
  Authentication Type: EAP
  EAP Type: -
  Account Session Identifier: -
  Logging Results: Accounting information was written to the local log file.
  Reason Code: 34
  Reason: The user or computer account that is specified in the RADIUS Access-Request message is disabled.

Event Xml:
<Event xmlns="">
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <TimeCreated SystemTime="2015-09-24T21:35:32.847063700Z" />
    <Correlation />
    <Execution ProcessID="620" ThreadID="6436" />
    <Security />
    <Data Name="SubjectUserSid">S-1-5-21-746137067-1592454029-725345543-501</Data>
    <Data Name="SubjectUserName">
    <Data Name="SubjectDomainName">USA</Data>
    <Data Name="FullyQualifiedSubjectUserName">USA\rename_guest</Data>
    <Data Name="SubjectMachineSID">S-1-0-0</Data>
    <Data Name="SubjectMachineName">-</Data>
    <Data Name="FullyQualifiedSubjectMachineName">-</Data>
    <Data Name="MachineInventory">-</Data>
    <Data Name="CalledStationID"></Data>
    <Data Name="CallingStationID">A0-39-F7-21-4D-B8</Data>
    <Data Name="NASIPv4Address"></Data>
    <Data Name="NASIPv6Address">-</Data>
    <Data Name="NASIdentifier">002722f2bf98</Data>
    <Data Name="NASPortType">Wireless - IEEE 802.11</Data>
    <Data Name="NASPort">0</Data>
    <Data Name="ClientName">router-2</Data>
    <Data Name="ClientIPAddress"></Data>
    <Data Name="ProxyPolicyName">Secure Wireless Connections</Data>
    <Data Name="NetworkPolicyName">-</Data>
    <Data Name="AuthenticationProvider">Windows</Data>
    <Data Name="AuthenticationServer"></Data>
    <Data Name="AuthenticationType">EAP</Data>
    <Data Name="EAPType">-</Data>
    <Data Name="AccountSessionIdentifier">-</Data>
    <Data Name="ReasonCode">34</Data>
    <Data Name="Reason">The user or computer account that is specified in the RADIUS Access-Request message is disabled.</Data>
    <Data Name="LoggingResult">Accounting information was written to the local log file.</Data>
Who is Participating?

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

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.

Chris HInfrastructure ManagerCommented:
Configure Wireless Clients running Windows 7 and Windows Vista for PEAP-TLS Authentication

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
pramod1Author Commented:
user is using windows 8 machine
pramod1Author Commented:
reason Code: 22
  Reason: The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

pramod1Author Commented:
user is using windows 8
Craig BeckCommented:
The log you posted said:

Reason: The user or computer account that is specified in the RADIUS Access-Request message is disabled

Now are you saying you're getting a different error?

The first error is self-explanatory.

The second error means your network access policy isn't configured to allow the EAP type you tried to connect with.
pramod1Author Commented:
it is working with windows 7 fine not with windows 8
pramod1Author Commented:
I've requested that this question be deleted for the following reason:

i had put wrong question, i need to raise another question regarding exact problem
Seth SimmonsSr. Systems AdministratorCommented:
i had put wrong question

the question you just opened is exactly the same as this
why open a new one?  i think craig has been helpful thus far in assisting with the messages you are receiving
pramod1Author Commented:
windows 7 users machine are able to connect but not windows 8 machines
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
Windows Server 2012

From novice to tech pro — start learning today.