to:[EMAIL PROTECTED]
> Sent: Thursday, February 01, 2007 5:07 PM
> To: King, Michael
> Subject: RE: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
>
> Is it required that domain computers be allowed? Most of the college
> owned laptops are shared laptops.
>
> -
ged on to the computer before.
-Original Message-
From: Michael Griego [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 2:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
Dumb question... In your 802.1x configuration on
Sent: Thursday, February 01, 2007 3:48 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
>
> Hey, what user's do you have in your IAS's remote access policy?
>
> Do you have DOMAIN COMPUTERS allowed? (It's
t: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
Hi Lee,
Set the following registry key to "1".
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\EAPOL\EnableFileTracing
This will enable the following trace file:
c:\windows\tracing\eapol.log
Please post the log file here and I w
42 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
>
> I've changed the name and marked out the ip addresses.
>
> Here is an example of the deny
>
> User host/bob_10884.central.edu was denied access.
> Fully
42 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
>
> I've changed the name and marked out the ip addresses.
>
> Here is an example of the deny
>
> User host/bob_10884.central.edu was denied access.
> Fully-Q
Hi Lee,
Set the following registry key to "1".
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\EAPOL\EnableFileTracing
This will enable the following trace file:
c:\windows\tracing\eapol.log
Please post the log file here and I will take a look.
Regards,
Tom Rixom
PS. I am almost sure no confi
ed the name and marked out the ip addresses.
-Original Message-
From: Doug Payne [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 3:19 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
On 01/02/2007 3:32 PM, L
On 01/02/2007 3:32 PM, Lee Badman wrote:
Automatically Use My Windows Credentials- implies that the same user
name and password used to simply open up Windows is the same used to
login to the network, like against AD- which is not always the same (in
our case it is very likey almost never the sa
ISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
Automatically Use My Windows Credentials- implies that the same user
name and password used to simply open up Windows is the same used to
login to the network, like against AD- which is not always the same (in
dman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 01, 2007 12:39 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
>
> On the login box- which is preceeded by "Click here to select a
> certificate or other
Michael Griego [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 2:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
Dumb question... In your 802.1x configuration on your Windows
laptops, you *do* have both "Authenticate
2007 2:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
Dumb question... In your 802.1x configuration on your Windows
laptops, you *do* have both "Authenticate as a machine..." and
"Automatically use my Windows credentials
SERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
On the login box- which is preceeded by "Click here to select a
certificate or other credential" balloon pop-up, we inititially shot
ourselves in the foot somewhat as part of our Novell client build
wa
07 12:39 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
On the login box- which is preceeded by "Click here to select a
certificate or other credential" balloon pop-up, we inititially shot
ourselves in the foot somewhat as par
On the login box- which is preceeded by "Click here to select a
certificate or other credential" balloon pop-up, we inititially shot
ourselves in the foot somewhat as part of our Novell client build was a
registry tweak to disable such pop ups (this was done long before .1x
was even a twinkle in th
I would think this would be a RADIUS /IAS Issue. I do ths almost daily: Add a
temporary user to AD/ACS/RADIUS and log in with my WZC utility. It prompts on
the first login attempt for my uname/pw and to verify the cert. However, this
box does not often show itself easily and seems to hide be
-Original Message-
From: "Lee Weers" <[EMAIL PROTECTED]>
To: "WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU"
Sent: 2/1/2007 10:48 AM
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
I set this gpo, and the login scripts are still not running, and it
still didn'
fo and his keychain.
-Original Message-
From: Michael Griego [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 8:32 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
I took a quick look, and the GPO is "Always wait
1/31/2007 6:52 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
We push a group policy to all of our machines to re-enable the
Windows-2000-esque behavior that forces the client to wait until
network connectivity is established before
Is the GPO setting to have Fastboot disabled? We have this set so that
GPO's get processed in order.
-Original Message-
From: Michael Griego [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 31, 2007 5:53 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Pro
chael Griego [mailto:[EMAIL PROTECTED]
Sent: Wed 1/31/2007 6:52 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems with Windows 802.1x supplicant
We push a group policy to all of our machines to re-enable the
Windows-2000-esque behavior that forces the client to wait
We push a group policy to all of our machines to re-enable the
Windows-2000-esque behavior that forces the client to wait until
network connectivity is established before presenting the login
screen. I don't remember the exact GPO off the top of my head, but
it does allow our wireless/802.
Lee,
The Windows 802.1x supplicant operates by default with some annoying timers
that are nearly always the cause of your #1 and #2 issue. Essentially the
system starts and the supplicant allows authentication as the computer account
with a timer counting down. IF the timer reaches zero bef
24 matches
Mail list logo
