Try to see if access is denied to this section of the registry. I don t know if mandatory profile locks down the registry but with that setup the users will need access to HKEY_CURRENT_USER\Software\Microsoft\EAPOL\UserEap Info
It is a small 73.69 MB file that will take some time.
Step 3: Downloading of the executable file will start shortly. Step 2: Click on Download, a new webpage will open with different installers of Wireshark. Will crack out Wireshark/Process Monitor tomorrow and figure this out, but kind of hopeful someone here might well have experienced this before? Step 1: Visit the official Wireshark website using any web browser. Rather odd and rather frustrating - the lack of anything on Google makes me wonder if it mightn't be an SP3 foible, but annoyingly I don't have any SP2 machines immediately to hand. Simply changing the profile to a normal roaming profile (NTUSER.MAN -> NTUSER.DAT, no other changes) results in everything working fine with successful authentication, and connection, etc. When a user logs on with a mandatory profile the RADIUS server (IAS on 2008) just sees repeated attempts to authenticate, but there's never an IAS_SUCCESS event indicating a proper connection (the clients stall at the 'validating identity' stage). The next Wireshark major release will be Wireshark 3.0 its preview releases have numbers such as 2.9.0. Anyone ever had problems with 802.1x (EAP-MS-CHAPV2) user authentication over wireless not working when using mandatory user profiles (WinXP, SP3)?
0 kommentar(er)
