Home > Event Id > Event Id 6273 Reason Code 16

Event Id 6273 Reason Code 16


In the Logon Hours dialog box, configure the days and times when the user is permitted to access the network. Event ID 6273 Reason Code 48 (bad network policy) If you receiveEvent ID 6273withReason Code 48when testing with theRADIUS Testfeature on Dashboard, this is usually indicative of an incorrectly configured Network To resolve, see the below KB articleson adding a RADIUS client and setting static IP addresses on access points. We use the same SSID enrolled over GPO. have a peek here

Use the information provided in Event Viewer to check that the user or computer credentials have not expired. Thanks Tiger Li Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your This documentation is archived and is not being maintained. Community Additions ADD Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful?

Event Id 6273 Reason Code 16

This can be beneficial to other community members reading the thread. It just fails when using a cert from the new server. Event ID 6273 Reason Code 66 (auth settings mismatch) If you receiveEvent ID 6273withReason Code 66when testing with theRADIUS Testfeature on Dashboard, this is usually indicative of the authentication settings incorrectly Please share website feedback current community blog chat Server Fault Meta Server Fault your communities Sign up or log in to customize your list.

Thanks.Clarification: Microsoft doesn't own any liability & responsibility for any of my posting. Search the Community Knowledge Base Here: Community Knowledge BaseValidated Reference Design Guides : http://community.arubanetworks.com/t5/Validated-Reference-Design/tkb-p/Aruba-VRDs Alert a Moderator Message 8 of 14 (14,487 Views) Reply 0 Kudos Excl Occasional Contributor II Posts: I was able to convince our Windows Server admin to install the CA server as Enterprise CA & not as Standalone CA. Event Id 18 Nps Thanks.

Check EAP log file for EAP errors. (Authentication Method is PEAP) I have sniffed the authentication process: Switch sends "Radius Access Request" to NPS NPS answers with "Radius Access Challenge" Switch Network Policy Server Denied Access To A User 6273 Which kind of switches are you using? Meanwhile, could you upload the captured traffic data and event logs on clients which relate with this issue to the links below for further investigation: https://sftus.one.microsoft.com/choosetransfer.aspx?key=0d0fd4f4-5de2-4520-8415-5d59c3d8224a Password: Gpl[ImhNTQC Thanks. If they don't, deploy the cert there with a GPO and see if that solves the problem. 0 Message Author Comment by:Bitfarmer ID: 358158582011-05-23 You are correct, the Cert wasn't

Saturday, December 11, 2010 12:42 PM Reply | Quote Answers 0 Sign in to vote No, unfortunately not yet. Event Id 6273 Reason Code 48 twice) * I always thought PEAP would establish a TLS tunnel before authentication? I selected the cert for EAP from this new box. Kind regards, Dagmar Tuesday, December 14, 2010 8:59 PM Reply | Quote 0 Sign in to vote Hi Dagmar, Thank you for your update.

Network Policy Server Denied Access To A User 6273

The default NPS log file location is %Systemroot%Windows\system32\LogFiles. But I don´t know. Event Id 6273 Reason Code 16 Alert a Moderator Message 7 of 14 (14,491 Views) Reply 0 Kudos cjoseph Guru Elite Posts: 19,769 Registered: ‎03-29-2007 Re: PEAP authentication failure - Reason code 23 Options Mark as New Event Id 6273 Reason Code 22 Once the server was integrated with Active Directory and we requested the Cert as per procedure (used by Windows) and not using the Web method.

Marked as answer by Dagmar Heidecker Saturday, February 12, 2011 10:09 AM Saturday, February 12, 2011 10:08 AM Reply | Quote All replies 1 Sign in to vote Hi, after having navigate here All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback TechNet Products Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server SharePoint Products Skype for Business The solution, which seemed like a good one at the time, was to stand up a new server, and because of equipment limitations, put the CA and NPS roles on it. After that I have not heard from you again. Event Id 6273 Reason Code 65

To resolve this, a certificate will need to be installed or renewed on your NPS server, in order to establish TLS. Mismatch in Authentication Settings 7. Alert a Moderator Message 5 of 14 (14,497 Views) Reply 0 Kudos cjoseph Guru Elite Posts: 19,769 Registered: ‎03-29-2007 Re: PEAP authentication failure - Reason code 23 Options Mark as New http://0pacity.com/event-id/event-id-324-opensqlserverinstanceregkey-getregkeyaccessmask-failed-reason-2.html Want to help shape what #GenMobile can do?

Article by: Exclaimer Is your Office 365 signature not working the way you want it to? Event Id 6273 Reason Code 66 But the client that would be ok on autonomous AP, goes not in RUN state on the WLC.It is the same GPO profile and the same NPS as RADIUS Server. I am currently looking into this issue and will give you an update as soon as possible.

Regards, Dagmar Wednesday, December 22, 2010 5:34 AM Reply | Quote 0 Sign in to vote Hi, is there something new going on?

To check if the network adapter is working: Click Start, then right-click Computer. Also checked that the cert existed in my DC's and it does. Thank you for your help! Nps Reason Code 65 In how many bits do I fit The Futuristic Gun Duel stuck with this limit of a sum .

NPS logs the following event:Event ID 6273, Reason Code 23, Reason: An error occured during the Network Policy Server use of the Extensible Authentication Protocol (EAP). When you locate the user or computer certificate that you want to examine, double-click the certificate to open it.Use the "Certificate Requirements for PEAP and EAP" in the NPS Help on Check that the domain controller is connected to the network. this contact form Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We

Using default 0[1980] 04-11 16:13:42:812: Trying to set LDAP encryption = 1[1980] 04-11 16:13:42:812: Setting localServerName.User to WIN-35M4P8MNI43$[1980] 04-11 16:13:42:858: LDAP connect succeeded.[1980] 04-11 16:13:42:858: Sending LDAP search to WIN-35M4P8MNI43.dc.lab.[1980] 04-11 To configure the NAS-Port-Type condition: Click Start, Administrative Tools, Network Policy Server. Thanks for you help.Ds Attachment: 130625-NPS Configuration.docx See More 1 2 3 4 5 Overall Rating: 5 (1 ratings) Log in or register to post comments Scott Fella Thu, 06/28/2012 - The NPS Log does not contain any errors.

I know I can get this to work if I set up an NPS server and choose a cert from my old cert server. We are using PEAP with server Cert for authentication. Of course, after doing this, and resolving the immediate crisis, we were getting reports that wireless access wasn't working anymore. The NAC device is working as a Radius proxy (and nothing else at this stage of the project).

If this option is selected, the Certificate Authority must be added to the client's list of Trusted Root Certification Authorities. I've registered NPS in AD. It helped me a lot to find what was misconfigured on my NPS. All rights reserved.

The strange thing is I don't see the default cert that works on my clients, I see the one I created after the fact. 0 Message Author Closing Comment by:Bitfarmer If the Ethernet cable is not plugged into the adapter, plug it in. Client:, TEST.x.x.x NPS: NAC: I have also uploaded the client's svchost_RASTLS.log. The Server Certificate would not be checked and the NPS config was checked with the infos from the postings here.I see in the debug logs from the wlc the similar messages

If the connection method is not allowed by network policy, see the section titled "Add or change a connection method." Network access server is under attack Check the NPS log file Events Experts Bureau Events Community Corner Awards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts Wednesday, December 15, 2010 9:40 AM Reply | Quote 0 Sign in to vote Hi Dagmar, We may need more information for troubleshooting. But I'm still not able to connect, same error in NPS log file.

I just link to it ;) Next, you need to ensure that in your remote access policy the correct certificate is used.