A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Configuring 802.1X Authentication



 
 
Thread Tools Display Modes
  #1  
Old March 22nd 10, 05:21 PM posted to microsoft.public.windowsxp.network_web
Camerons
external usenet poster
 
Posts: 2
Default Configuring 802.1X Authentication

We are currently using Windows XP Professional SP3 with Client Side
Extensions installed against a 2003 Active Directory functional level domain

We are attempting to implement an 802.1X certificate based authentication
scheme accross our enviroment for both our wired and wireless connection.
Unfortuatley the people who we rent active directory from are unwilling to
setup a 2008 Active Directory functional level domain controller or apply
the requried schema extension necessary so that I could apply the 802.3X
Wired Authentication GPO

I've done much research on this, will very little productive information.

What information I have found describes the same process that if you enable
the Wired AutoConfig service which enable the Authentication Tab for your
network card, that authentication changes are stored in the registry in the
following location

HKLM\SOFTWARE\Microsoft\EAPOL\Parameters\Interface s\YOURNIC\

I tried replicating the settings on my desktop and while I could make
changes via the GUI, I could not find those changes replicated in the
specified location or for that matter in any place in the registry. I
thought this maybe had to do with image domain added workstation, maybe a
seperate GPO was doing something. So this morning I setup a clean box with a
default install of Windows XP SP2 not attached to any domain/workgroup.

Unfortuatley I've found that the same situation has occured. I should also
say this is with using either PEAP or Certificate as the authenetication
method.

I was hoping someone might be to shed some light as to why my registry isn't
updating, before I have to place a call with Microsoft and use up support
hours.

For more information the most productive post I've been able to find on this
topic is:
http://www.derkeiler.com/Newsgroups/...5-06/0126.html
Thanks.


Ads
  #2  
Old March 31st 10, 04:05 PM posted to microsoft.public.windowsxp.network_web
Eric Geier
external usenet poster
 
Posts: 2
Default Configuring 802.1X Authentication

I'm not sure about the registry, but you might find using a hosted
RADIUS/802.1X service better than setting up your own server.
AuthenticateMyWiFi from NoWiresSecurity is one choice:
http://www.NoWiresSecurity.com

"Camerons" wrote:

We are currently using Windows XP Professional SP3 with Client Side
Extensions installed against a 2003 Active Directory functional level domain

We are attempting to implement an 802.1X certificate based authentication
scheme accross our enviroment for both our wired and wireless connection.
Unfortuatley the people who we rent active directory from are unwilling to
setup a 2008 Active Directory functional level domain controller or apply
the requried schema extension necessary so that I could apply the 802.3X
Wired Authentication GPO

I've done much research on this, will very little productive information.

What information I have found describes the same process that if you enable
the Wired AutoConfig service which enable the Authentication Tab for your
network card, that authentication changes are stored in the registry in the
following location

HKLM\SOFTWARE\Microsoft\EAPOL\Parameters\Interface s\YOURNIC\

I tried replicating the settings on my desktop and while I could make
changes via the GUI, I could not find those changes replicated in the
specified location or for that matter in any place in the registry. I
thought this maybe had to do with image domain added workstation, maybe a
seperate GPO was doing something. So this morning I setup a clean box with a
default install of Windows XP SP2 not attached to any domain/workgroup.

Unfortuatley I've found that the same situation has occured. I should also
say this is with using either PEAP or Certificate as the authenetication
method.

I was hoping someone might be to shed some light as to why my registry isn't
updating, before I have to place a call with Microsoft and use up support
hours.

For more information the most productive post I've been able to find on this
topic is:
http://www.derkeiler.com/Newsgroups/...5-06/0126.html
Thanks.


.

  #3  
Old March 31st 10, 04:05 PM posted to microsoft.public.windowsxp.network_web
Eric Geier
external usenet poster
 
Posts: 2
Default Configuring 802.1X Authentication

I'm not sure about the registry, but you might find using a hosted
RADIUS/802.1X service better than setting up your own server.
AuthenticateMyWiFi from NoWiresSecurity is one choice:
http://www.NoWiresSecurity.com

"Camerons" wrote:

We are currently using Windows XP Professional SP3 with Client Side
Extensions installed against a 2003 Active Directory functional level domain

We are attempting to implement an 802.1X certificate based authentication
scheme accross our enviroment for both our wired and wireless connection.
Unfortuatley the people who we rent active directory from are unwilling to
setup a 2008 Active Directory functional level domain controller or apply
the requried schema extension necessary so that I could apply the 802.3X
Wired Authentication GPO

I've done much research on this, will very little productive information.

What information I have found describes the same process that if you enable
the Wired AutoConfig service which enable the Authentication Tab for your
network card, that authentication changes are stored in the registry in the
following location

HKLM\SOFTWARE\Microsoft\EAPOL\Parameters\Interface s\YOURNIC\

I tried replicating the settings on my desktop and while I could make
changes via the GUI, I could not find those changes replicated in the
specified location or for that matter in any place in the registry. I
thought this maybe had to do with image domain added workstation, maybe a
seperate GPO was doing something. So this morning I setup a clean box with a
default install of Windows XP SP2 not attached to any domain/workgroup.

Unfortuatley I've found that the same situation has occured. I should also
say this is with using either PEAP or Certificate as the authenetication
method.

I was hoping someone might be to shed some light as to why my registry isn't
updating, before I have to place a call with Microsoft and use up support
hours.

For more information the most productive post I've been able to find on this
topic is:
http://www.derkeiler.com/Newsgroups/...5-06/0126.html
Thanks.


.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 09:58 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.