11-15-2012 11:26 AM
I am having trouble with 802.1x Authentication on Samsung Galaxy SIII Smart Phones.
After setting the wireless settings on the phone it can take numerous tries before the device will connect.
Each failed attempt is according to the phone due to an authentication error but without making any changes to the settings and simply touching the connect button again and again, the device will eventually connect. There is no record of an Authentication error on My RADIUS Servers. There isn't even a log entry for the Authentication attempt so this implies that the controller does not forward the auth request to the RADIUS server and leads me to think the problem is likely with the 802.1x profile on my controllers.
Thing is that this only seems to be happening with Android devices.
This specific phone is a "MUST FIX" because we have deployed a couple of hundred of them across our organization.
Anyone had any similar experiences with the Galaxy SIII (Samsung SGH-I747M)? Better yet, anyone have a solution???
Thanks in advance.
Solved! Go to Solution.
11-15-2012 12:54 PM
Similar experience with my own Samsung S3 on our 802.1x network as well.
The only thing I can possibly think of is to enable the "Validate PMKID" option but I don't want to turn that on as I am the only one out of 600 users who connects their phone to the corporate wireless, and that's really only for testing when I am at another site to make sure the vlans are correct, etc.
11-16-2012 03:28 PM
I see this effect too but only the Sprint phones of this flavor do this...
Also, a few other Sprint Android phones will not connect to save their life.
We use Windows 2008 as our .1x security
11-16-2012 04:10 PM
Please open a TAC case so that they can get the specifics of your deployment. They can seek and uncover details that would take a great deal of time on this forum.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
11-26-2012 05:59 AM
Opened a TAC with both Aruba and Samsung.
Samsung tells me that Telus Mobility, whom we have our S3's with will be pushing out an update over the next couple of days.
This update is supposed to solve a number of issues so hopefully roaming on 802.1x networks will be one of the fixes.
04-29-2013 06:56 PM
Sorry for re-opening this post. We don't use 802.1x but we are also encountering the same sympthom. The phone just won't connect and will just say Authentication error of some sort. However, this happens intermittently. This never happen to any of our iOS devices.
Here's the phone info:
Samsung Galaxy S3
Model Number: GTI9300
Android Version: 4.1.2
Baseband version: I9300XXELLA
AP135, with WPA2 PSK
04-29-2013 07:52 PM
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA