04-17-2009 09:02 AM
We are rolling out RADIUS/802.1x wireless lan in our enterprise. The wireless settings are deplyed via AD grouo policy - no problems there.
I have an issue when i configure my access connections (ver 5.21) on my T61 machine. I configure AC to use Windows wireless security settings whcih are picked up correctly. The issues occur when i switch from this profile to another profile for exampls and vice versa. AC seems to think that i need to configure my wlan security settings each time i switch to that profile and wont connect. I get an error message:
The SSID 'WM2009' selected for this profile must be configured in windows. Click OK to configure the wireless settings in Windows'.
I know that the wireless settings are fine, as i can connect with the window wireless client fine - its just AC that has the issue.
Any ideas appreciated!
04-17-2009 11:56 AM
Domain policy wireless profiles are not compatible with Access Connections.
The problem stems that Domain profiles are stored in a different part of the registry than a locally created WZC profile. Since these are part of the domain policy, they cannot be altered locally. Microsoft wouldn't provide Lenovothe encryption used (for obvious security reasons), so the domain policy based profiles can't be manipulated by Access Connections.
But we do provide an ADM template that can be used to do much the same things.
04-20-2009 08:29 AM
Hello Again - quick question regarding configuring 802.1x AC profiles...
I have managed to get this to work although seems quite flaky especially on older models, ie T60. When you configure an 802.1x profile can so make the computer connect to WLAN before domain login?
When i was using the windows configuration it does this whcih is great, so GPO, logon scripts can run.
I cant see any setting for this.
Do you have some ideas
04-24-2009 07:06 AM
Go into Global Settings and the second check box will enable the TVT Gina. You can then use logon credentials for 802.1x authentication and connect wirelessly so domain scripts will run.
Note: there are some functions (like installing software via domain policy) that have to be done over ethernet. Just FYI..