Windows Workstation Authentication
I have 802.11 authentication set up using an eDirectory backend and it all works except for one thing. When a user logs in to a Windows computer using a windows account that does not exist in eDirectory the authorization fails. Since the locally logged on user does not exist in eDirectory, authorization fails before the user is prompted when initially trying to connect to the wireless. Instead the workstation sends the user credentials that were used to log in locally to the radius server. Does anyone know if there is a way to configure the Windows wireless connection or the radius backend to force a prompt for authorization? Thanks for any assistance. Dan
There is a setting in Windows wireless setup to "Automatically use my Windows logon name and password". If it is check-marked it will use the Windows login. Mearl Danner Systems Programmer Samford University Technology Services http://www.samford.edu From: freeradius-users-bounces+jmdanner=samford.edu@lists.freeradius.org [mailto:freeradius-users-bounces+jmdanner=samford.edu@lists.freeradius.org] On Behalf Of Dan Lietz Sent: Thursday, October 31, 2013 3:27 PM To: freeradius-users@lists.freeradius.org Subject: Windows Workstation Authentication I have 802.11 authentication set up using an eDirectory backend and it all works except for one thing. When a user logs in to a Windows computer using a windows account that does not exist in eDirectory the authorization fails. Since the locally logged on user does not exist in eDirectory, authorization fails before the user is prompted when initially trying to connect to the wireless. Instead the workstation sends the user credentials that were used to log in locally to the radius server. Does anyone know if there is a way to configure the Windows wireless connection or the radius backend to force a prompt for authorization? Thanks for any assistance. Dan
Hi Mearl, I'm not seeing a setting for that, can you send a screen shot of it? Thanks. Dan Lietz Ingham Intermediate School District Network Engineer From: Danner, Mearl [mailto:jmdanner@samford.edu] Sent: Thursday, October 31, 2013 4:38 PM To: FreeRadius users mailing list Subject: RE: Windows Workstation Authentication There is a setting in Windows wireless setup to "Automatically use my Windows logon name and password". If it is check-marked it will use the Windows login. Mearl Danner Systems Programmer Samford University Technology Services http://www.samford.edu From: freeradius-users-bounces+jmdanner=samford.edu@lists.freeradius.org<mailto:freeradius-users-bounces+jmdanner=samford.edu@lists.freeradius.org> [mailto:freeradius-users-bounces+jmdanner=samford.edu@lists.freeradius.org] On Behalf Of Dan Lietz Sent: Thursday, October 31, 2013 3:27 PM To: freeradius-users@lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org> Subject: Windows Workstation Authentication I have 802.11 authentication set up using an eDirectory backend and it all works except for one thing. When a user logs in to a Windows computer using a windows account that does not exist in eDirectory the authorization fails. Since the locally logged on user does not exist in eDirectory, authorization fails before the user is prompted when initially trying to connect to the wireless. Instead the workstation sends the user credentials that were used to log in locally to the radius server. Does anyone know if there is a way to configure the Windows wireless connection or the radius backend to force a prompt for authorization? Thanks for any assistance. Dan
Its under the PEAP advanced properties settings or some such... easily found after just a few clicks on the interface. If you Google for Windows 802.1X PEAP manual instructions you're sure to find examples of the 'how to configure windows 802.1X in 21 steps' alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
LOL too right :) If you are doing EAP-PEAP-MSChapV2 feel free to review our configuration documents for our WPA2-Enterprise network GTwifi. http://www.lawn.gatech.edu/help/gtwifi (with troubleshooting guides) On 11/05/2013 01:01 PM, Alan Buxey wrote:
Its under the PEAP advanced properties settings or some such... easily found after just a few clicks on the interface. If you Google for Windows 802.1X PEAP manual instructions you're sure to find examples of the 'how to configure windows 802.1X in 21 steps'
alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 5 Nov 2013, at 18:01, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
Its under the PEAP advanced properties settings or some such... easily found after just a few clicks on the interface. If you Google for Windows 802.1X PEAP manual instructions you're sure to find examples of the 'how to configure windows 802.1X in 21 steps'
Bah back in my day it was 40 steps and one of them involved starting additional services! Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
On Tue, Nov 05, 2013 at 06:15:09PM +0000, Arran Cudbard-Bell wrote:
On 5 Nov 2013, at 18:01, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
If you Google for Windows 802.1X PEAP manual instructions you're sure to find examples of the 'how to configure windows 802.1X in 21 steps'
Bah back in my day it was 40 steps and one of them involved starting additional services!
Doesn't matter how many steps it takes, Microsoft still grease them up good and proper, so you end up sitting on the floor with a painful backside, wondering what just happened. To top if off, wireless still doesn't work properly, so you have to crawl back to the top and try again. -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Hi,
Its under the PEAP advanced properties settings or some such... easily found after just a few clicks on the interface. If you Google for Windows 802.1X PEAP manual instructions you're sure to find examples of the 'how to configure windows 802.1X in 21 steps'
Bah back in my day it was 40 steps and one of them involved starting additional services!
;-) my favourite is still the 'wireless zero configuration' service (WZC) being required for 802.1X on the WIRED interface! duh! go figure. they fixed that after WinXP though at least! alan
participants (7)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan Buxey
-
Arran Cudbard-Bell -
Dan Lietz -
Danner, Mearl -
John Douglass -
Matthew Newton