Forum Discussion

cphillips19_137's avatar
cphillips19_137
Icon for Nimbostratus rankNimbostratus
Feb 24, 2015

APM Always connected mode

Hey support,

 

Wondering if anyone is using the always connected mode for windows big IP edge client? When we create a package with this feature off, everything works as desired. The auto-connect button stays selected for users and connects when the program sensing it is not on the domain (at home for example).

 

When I create a new edge client package with "Enable always connected mode" selected I run into issues when computers are brought back into the office (on the domain). A popup senses it is on the local LAN and says disconnected but nothing works. Cannot ping default gateway (general failure). Nothing seems to work. (This does work when you take it out of the office domain). Am I missing a setting to allow computers to work as normal without any VPN features when this feature is enabled?

 

APM
big-ip edge client
design
security

7 Replies

Sort By
  • Nicolas_Berthie's avatar
    Nicolas_Berthie
    Historic F5 Account
    Feb 25, 2015

    Hello cphillips19,

     

    First of all, Devcentral is not F5 support, it is user community web site. You can reach F5 support at https://websuport.f5.com. Regarding your issue, I faced same issue and opened a ticket. There is a known bug when both 'Always Connected' and 'Location Awareness' are used. I encourage you to open a case.

     

    Nicolas

     

  • cphillips19_137's avatar
    cphillips19_137
    Icon for Nimbostratus rankNimbostratus
    Feb 25, 2015

    Thanks Nicolas,

     

    Apologies for the "Hey Support" line. Must have wrote it out of habit. Just wanted to see if anyone in this community had experienced issues with "Always Connected" before I went and opened a ticket with support.

     

  • cphillips19_137's avatar
    cphillips19_137
    Icon for Nimbostratus rankNimbostratus
    Mar 06, 2015

    Answer for users running into this same issue. ("Always Connected" used with location awareness on the local LAN locking down clients). There is a Bug ID 488866 for this issue.

     

  • Bjarne_Talg__21's avatar
    Bjarne_Talg__21
    Icon for Nimbostratus rankNimbostratus
    Apr 15, 2015
    Hi Cphillips19 I have the same problem as you. Did you get a solution for this at F5 Support? Bjarne
  • cphillips19_137's avatar
    cphillips19_137
    Icon for Nimbostratus rankNimbostratus
    Apr 15, 2015
    Hi Bjarne, I opened a ticket with F5 support and unfortunately this is a known bug. You cannot use location awareness with the always-on client. I heard they may be working on this issue for the next release. We had to postpone the "always-on" client deployment and just use a normal client with the auto-connect features (obviously this gives the end user power to manually turn off connection if they want.)
  • cphillips19_137's avatar
    cphillips19_137
    Icon for Nimbostratus rankNimbostratus
    Apr 15, 2015
    Bug ID 488866 if you want to have your local F5 system engineer to keep an eye on it for you.
  • Bjarne_Talg__21's avatar
    Bjarne_Talg__21
    Icon for Nimbostratus rankNimbostratus
    Apr 17, 2015
    Thank you cphilliips. Then I must do the same as you and use the Auto connect feature until the bug is fixed. Bjarne