Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 26 subscribers
  • Views 5917 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with the Android CAA client

TroyCarpenter

I have downloaded and installed the Sophos Network Agent on android.  On at least two Samsung devices, the program did not register for the .scc extension for the certificate, and I have to force the association so that the agent would install the certificate.

Secondly, even with the reconnect and persistent notification options selected, there are still times (maybe when firewall policies are changed...see https://community.sophos.com/products/xg-firewall/f/124/p/75212/305212#305212) when the agent disconnects.  Worse still, the disconnect seems to kick out the persistent notification and the client is left wondering why network access has suddenly stopped.  Even though the reconnect option is selected, the agent routinely does not reconnect, and the user has to re-run the agent to get it working.

However, even with the re-run of the agent, sometimes it gets stuck trying to connect to XG.  It gives a yellow indication with a distractor that never goes away.  In those cases, I've had to use a task manager to kill the agent and restart it.  Usually it connects right away after the second try.

Is anyone else having similar issues?  I'm getting lots of complaints about no-network connectivity, and after investigating, more times than not this ends up being the cause.



This thread was automatically locked due to age.
  • 0

    Hi Troy,

    Seems like you are on a testing spree. Provide me some time to recreate this and update you accordingly.

    Thanks

  • 0 in reply to sachingurung

    Not so much a testing spree as I turned it on for about 6 users (including myself), and now I'm answering questions about its functionality.

    Late last night I found that the timeout setting for Web Clients, and I can see how that might be playing into the disconnects.  I know the agent can tell if the disconnect was from a timeout, and in that case it might not be prudent to reconnect automatically if the user has a time quota.

    But, the agent not being able to log back in is real.  I had another user show it to me this morning.  Agent said it couldn't log in.  Once we killed the agent on the phone and re-ran it, it connected immediately.

    Right now I've instructed people to have easy access to the agent, either by putting it on a home screen or other type of shortcut so they can run it when they discover they are no longer connected.