cancel
Showing results for 
Search instead for 
Did you mean: 

Most mobile clients stopped working with a mag2600 yesterday

Highlighted
Occasional Contributor

Most mobile clients stopped working with a mag2600 yesterday

I have a client with a MAG2600 that was running 7.1R1. They have android and IOS mobile clients that worked fine until yesterday. Supposedly no changes were made, and desktop clients work fine. I upgraded the device to 7.4R8, but the devices still won't conenct. I had a motorola xoom conenct briefly after a pulse reinstall, but then wouldn't connect again. A samsung galazy however works fine. Ipad doesn't work.

The error I was getting was "Browser on host xx.xx.xx.xx is not supported for Host Checker or Cache Cleaner"

Host checker is not in use however, and neither is cache cleaner.  I don't see as many instances of that post-upgrade, but the mobile devices refuse to connect.

The MAG has a self-signed ssl cert, not a purchased one if that matters. Since desktops and the samsung galaxy conenct, I'm inclined to not point to a config issue, but more a software bug perhaps?

Anyone else having this issue recently?

5 REPLIES 5
Highlighted
Frequent Contributor

Re: Most mobile clients stopped working with a mag2600 yesterday

Do you have any useragent-string restricitions on your realm or role?





---------------------------------------------------
Please mark this post as 'accepted solution' if my input answers your question!
A kudo would be nice if you think I deserve it.
---------------------------------------------------
2 A/P clustered 6500, 7.4R9.1
2 A/P clustered 2500, 8.0R3.1 LAB
Highlighted
Regular Contributor

Re: Most mobile clients stopped working with a mag2600 yesterday

are there anyother realms configured under the same sign in url which uses hostchecker?


Highlighted
Regular Contributor

Re: Most mobile clients stopped working with a mag2600 yesterday

Hi,

How do you access from the mobile devices is it from browser or pulse?

if this is pulse what version pulse are you reunning on the mobile devices?

Do let us knowOS and  its version on the mobile devices as well.

Regards,

SVK

Highlighted
Occasional Contributor

Re: Most mobile clients stopped working with a mag2600 yesterday

No, any useragent is allowed. No host checker policies either. What was interesting is that in the logs before I did the upgrade it was saying that hostchecker wasn't supported on the client device, but no HC was enabled, so I don't know if that was just an informational message or something else. Not really seeing that on the upgraded code.

Highlighted
Occasional Contributor

Re: Most mobile clients stopped working with a mag2600 yesterday

The MAG2600 is running 7.4R8, which is the J-Tac recommended version, and the clients, both android and iOS are running the latest versions of the pulse client from the app store on their respective devices. So I think for iOS that's going to be 5.0.2 according to my phone. Should they be using a different client other than what's in the app store?

What I see in the user access logs is a user connects, then the client disconnects. I am not seeing the authentication and the assignment of roles to the user(s) in question. On their devices they are getting a not supported message at times.

I had one user remove the pulse app from his motorola xoom, re-install from app store, it connected once and then never again. Since the logs aren't giving me much, I'm having a hard time tracking this down.