Jump to content

Server 2008 NPS with wireless 802.1x authentication errors


Recommended Posts

Guest Roostermiester
Posted

I've setup Server 2008 NPS (which is also functioning as a DC) to

authenticate wireless clients through a Cisco 2106 wireless lan controller.

The computer certs are auto installed through Group Policy. However, when it

attempts to authenticate I recieve the following error:

 

Log Name: Security

Source: Microsoft-Windows-Security-Auditing

Date: 6/2/2008 12:24:38 PM

Event ID: 6273

Task Category: Network Policy Server

Level: Information

Keywords: Audit Failure

User: N/A

Computer: DC1.coaccess.com

Description:

Network Policy Server denied access to a user.

 

Contact the Network Policy Server administrator for more information.

 

User:

Security ID: NULL SID

Account Name: 99C4R41.coaccess.com

Account Domain: COACCESS

Fully Qualified Account Name: COACCESS\99C4R41.coaccess.com

 

Client Machine:

Security ID: NULL SID

Account Name: -

Fully Qualified Account Name: -

OS-Version: -

Called Station Identifier: 00-1F-CA-82-A1-80:coa

Calling Station Identifier: 00-90-96-A3-E4-1F

 

NAS:

NAS IPv4 Address: 10.10.230.6

NAS IPv6 Address: -

NAS Identifier: COAWLC-2106

NAS Port-Type: Wireless - IEEE 802.11

NAS Port: 1

 

RADIUS Client:

Client Friendly Name: COAWLC

Client IP Address: 10.10.230.6

 

Authentication Details:

Proxy Policy Name: Secure Wireless Connections Request

Network Policy Name: -

Authentication Provider: Windows

Authentication Server: DC1.coaccess.com

Authentication Type: EAP

EAP Type: -

Account Session Identifier: -

Reason Code: 8

Reason: The specified user account does not exist.

 

I haven't been able to come up with any good reason for the error. I do

recall having similar issues in a previous deployment and the solution was to

modify the computer name, but that has not worked in this case. Any ideas

what is causing this error?

Thanks

  • Replies 1
  • Created
  • Last Reply

Popular Days

Guest James McIllece [MS]
Posted

The NPS troubleshooting topic "Event ID 6273  NPS Authentication Status"

might be of some assistance to you.

 

http://technet2.microsoft.com/WindowsServe...eb1eec1033.mspx

 

Also, just for future reference, the IAS/NPS Usenet newsgroup is

microsoft.public.internet.radius

 

 

"Roostermiester" wrote:

<span style="color:blue">

> I've setup Server 2008 NPS (which is also functioning as a DC) to

> authenticate wireless clients through a Cisco 2106 wireless lan controller.

> The computer certs are auto installed through Group Policy. However, when it

> attempts to authenticate I recieve the following error:

>

> Log Name: Security

> Source: Microsoft-Windows-Security-Auditing

> Date: 6/2/2008 12:24:38 PM

> Event ID: 6273

> Task Category: Network Policy Server

> Level: Information

> Keywords: Audit Failure

> User: N/A

> Computer: DC1.coaccess.com

> Description:

> Network Policy Server denied access to a user.

>

> Contact the Network Policy Server administrator for more information.

>

> User:

> Security ID: NULL SID

> Account Name: 99C4R41.coaccess.com

> Account Domain: COACCESS

> Fully Qualified Account Name: COACCESS99C4R41.coaccess.com

>

> Client Machine:

> Security ID: NULL SID

> Account Name: -

> Fully Qualified Account Name: -

> OS-Version: -

> Called Station Identifier: 00-1F-CA-82-A1-80:coa

> Calling Station Identifier: 00-90-96-A3-E4-1F

>

> NAS:

> NAS IPv4 Address: 10.10.230.6

> NAS IPv6 Address: -

> NAS Identifier: COAWLC-2106

> NAS Port-Type: Wireless - IEEE 802.11

> NAS Port: 1

>

> RADIUS Client:

> Client Friendly Name: COAWLC

> Client IP Address: 10.10.230.6

>

> Authentication Details:

> Proxy Policy Name: Secure Wireless Connections Request

> Network Policy Name: -

> Authentication Provider: Windows

> Authentication Server: DC1.coaccess.com

> Authentication Type: EAP

> EAP Type: -

> Account Session Identifier: -

> Reason Code: 8

> Reason: The specified user account does not exist.

>

> I haven't been able to come up with any good reason for the error. I do

> recall having similar issues in a previous deployment and the solution was to

> modify the computer name, but that has not worked in this case. Any ideas

> what is causing this error?

> Thanks</span>

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...