04-29-2009 09:18 AM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
04-29-2009 10:35 AM
Yes I agree, the ProSet has proven to be unreliable in this case. On the other hand, the second set of users in this building, who do not share laptops, are using the full ProSet client and have had no issues.
(This issue with the ProSet client has forced me to look at using GPO and the Windows client.)
This building is a pure "N" environment and so MIMO (3x3) performance is important to me. By using the full ProSet client, I have more means available to me to tweak wireless radio's settings than using the Window's client alone.
I'm seeing 240+ Mbps (@ 5.0 GHz) versus around 120 Mbps (@ 5.0 GHz)
04-29-2009 11:18 AM
04-30-2009 06:29 AM
The Hardware is Intel 4965AGN and the software ver. is 12.4.
I'm using IxoChariot to test the bandwidth using multiple pairs.
I will not have the additional Window Client options available via GPOs, which you you may be thinking of, until we approve Vista/Win7.0 for roll-out to our laptops, which will be in another 5 years or so. ;)
The XP GPO is basically.... basic.
06-19-2009 11:56 AM
11-20-2009 11:04 AM
- Aruba Controller 3600
- windows 2003 domain
- windows 2003 w/Radius
- lenovo laptops w/windows xp sp3
- intel pro/wireless 3945ABG interfaces
- WPA2 w/AES
- EAP-MSCHAP v2
If I make the SSID Open it connects with no problem. Any help would be much appreciated!
11-20-2009 12:04 PM
Are you using a GPO to configure the wireless client?
To fix my problem....
1. Extended the Server 2003 AD schema to allow Server 2008/Vista group policies.
2. Created a XP wireless Group Policy Object, which configures the client for our Wireless settings, and linked it to the OUs that contain the laptops.
3. Removed the full Intel PROSet Client and left the driver.
4. Added 3 additional IAS servers to handle the additional authentication load.
Each time Group Policy updates it reinforces the wireless configuration and prevents the user from deleting or modifying the profile.
Since then I've tweaked Group Policy to filter out objects and grant/deny Group Membership, but the basic setup is still the same.