Hello again to everyone!
Problem seems to be solved after changing the Device certificate to the internal interface. I'm only wondering why it behaves like that.
Hi All,
Please refer the following KB which describes the behavior
http://kb.pulsesecure.net/KB21828
Thanks