Remote Access SSL VPN Static IP address results in route issues

When you do the ping which is not working, do you have the remote user (which has the static ip 172.16.101.2) connected via sslvpn tunnel ? When the ping is working, who has been assigned the ip 172.16.101.2 ?

IP 172.16.101.2 is when I do not use static IP address in ssl Global Config. It all uses 1 vpn account.
User A Using static ip: 172.16.101.142 cannot ping
User A Do not use static IP: 172.16.101.2 can ping

I realized that in the routing table there are only routing tun# as follows:

and I added a route using the command line: ip route add 172.16.101.128/25 via 0.0.0.0 dev tun0
It worked.

For users with static IP, the ping from the firewall (what is known as system generated traffic) will not work as there is no specific route setup for the static IP subnet. If the ping is from any LAN servers connected to the firewall, to the remote user, it will work. Do you have a use case for the ping from firewall to work or is it only for testing purpose ?