Wireless Access

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.

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.

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

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.

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.

 

We have updated the OS on our Galaxy S III phones to JellyBean.

This has solved the problem.

 

 

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

 

Aruba Setup:

AP135, with WPA2 PSK

 

---

@McArenas wrote:

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

 

Aruba Setup:

AP135, with WPA2 PSK

 

---

McArenas,

 

Please disable band-steering and spectrum load balancing to rule out poor coverage.

 

How long is the preshared key ?

18 chars long. 

 

I switched to a different SSID, with a shorter PSK, (10 chars), but still same problem. 

what can see when you run the show auth-tracebuf ?

Here an actual screenshot:

 

when a successful connection was made:

 

 

Here's the screenshot from the phone during error and during an error, there is nothing on the auth trace log with the specific mac address.

 

 

 

Have you removed any of the lower data rates under the SSID ? sometimes some devices don't like that.

 

What code are you running ?

 

Do you see anything in the logs ? logging level debugging user-debug <device mac address>

---

@vfabian wrote:

 

 

Have you removed any of the lower data rates under the SSID ? sometimes some devices don't like that.

 

What code are you running ?

 

Do you see anything in the logs ? logging level debugging user-debug <device mac address>

---

Here's a screencap of a particular SSID profile:

 

 

 

Sorry I didn't quite get it... which code?

 

How do I enable debugging level logging in our controllers?

 

Also, where can I read about the meaning of all those settings? Again, thanks for your guidance. 

 

thanks,

M

 

Sorry I didn't quite get it... which code?

I meant the AOS code version you are running 

 

(controller) #show version
Aruba Operating System Software.
ArubaOS (MODEL: Aruba7240-US), Version 6.2.0.3

 

How do I enable debugging level logging in our controllers?

 

(controller) (config) #logging level debugging user-debug <device mac address>

 

and then to view the logs generated :

 

(controller) #show logs user-debug all | include <device mac address>

 

Here's more info on how to debug:

http://www.arubanetworks.com/techdocs/ArubaOS_61/ArubaOS_61_CLI/logging.htm

https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/R-1119

https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/R-1155

 

---

@vfabian wrote:

 

Sorry I didn't quite get it... which code?

I meant the AOS code version you are running 

 

(controller) #show version
Aruba Operating System Software.
ArubaOS (MODEL: Aruba7240-US), Version 6.2.0.3

 

 

---

thanks for your patience Victor. Here's our AOS version:

ArubaOS (MODEL: Aruba6000), Version 6.1.3.3

 

M

I have attached the Aruba User guide which explains most of those settings. (page 155)

 

You can find all this info in the Aruba support site :

http://support.arubanetworks.com/DOCUMENTATION/

---

@vfabian wrote:

 

 

(controller) #show logs user-debug all | include <device mac address>

 

 

---

Here's the log when it won't connect:

 

McArenas,

 

Like I said before, PLEASE turn off Spectrum Load Balancing or Band Steering.  The Samsung might not like the deauth.  "Resource Constrained" is Spectrum Load Balancing or Band Steering activity.

 

---

@cjoseph wrote:

McArenas,

 

Like I said before, PLEASE turn off Spectrum Load Balancing or Band Steering.  The Samsung might not like the deauth.  "Resource Constrained" is Spectrum Load Balancing or Band Steering activity.

 

---

Thank you so much!  That fixed the problem.  I appreciate all the help!

Thanks! As additional note I have noticed that this problem is only happening to a room with an AP135. I tried to roam in other classrooms with other AP models. 61, 121 and 105, samsung connects without s problem.

I will try to turn off load and spectrum balancing as suggested. Thanks!

That was Spectrum Load Balancing in the Radio Profile and Band Steering in the Virtual AP profile.