All Topics » Pulse Policy Secure

host checker on andriod in clientless connection
Contributor (11)
Mar 19, 2014 1:43am




I am trying to use host checker on android devices (with MAG 4610). I try to use agentless connection and on my andriod mobile browser as I enter the credentials I get the following msg.


"Host Checker is not supported. Please contact your administrator"


How can I use host checker policies on andriod without junos pulse client software.




Arslan Nawaz

Contributor (11)
Mar 19, 2014 7:37pm

Hi Arslan


The error message is imperative!

Host checker is not supported in andriod devices without Junos Pulse clinet.

Pulse clinet is mandatory to have support for host checker in android devices.

And there is no workaround for it, thank you.


Note: If this answers your question, you could mark this as accepted solution, that way it benefits others as well. Kudos will be cool if I earned it!






Contributor (11)
Mar 19, 2014 9:59pm

Hi Arslan,


To add an update to previous post,  currently we don't have a puls e client for UAC for both L3 and L2 connection.


Pulse  mobile client is available only for SSL VPN connection however if you feel using hostchecker without using pulse on mobiles as a mandotory requirement I suggest you to work with your local juniper accoun team to know the support roadmap on this.


Hope this resolves your query.


Note: If I have answered your questions, you could mark this post as accepted solution, that way it could help others as well. Kudo will be a bonus thanks!


    Contributor (11)
    Mar 20, 2014 5:09am

    Thanks a lot Raveen and Kannan.


    Actually I want to use NAC for the guest users to access limited internet. Usually we can't bind guest to install client on their mobiles and at the same time we want some minimal compliance enforcement like not allow them to use P2P software, torrents etc. Obviously I have workaround and can control the access on layer 3 on SRX firewalls but I think It was better if we can enforce the compliance via MAG directly.


    Hopefully it will be in the future roadmap.