{"id":1938,"date":"2016-03-30T00:09:45","date_gmt":"2016-03-30T00:09:45","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=1938"},"modified":"2022-03-11T05:47:18","modified_gmt":"2022-03-11T05:47:18","slug":"ssl-vpn-98-no-more-addresses-fortigate","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/random\/ssl-vpn-98-no-more-addresses-fortigate","title":{"rendered":"Forticlient – SSL VPN 98% “no more addresses” fortigate"},"content":{"rendered":"

Users who could connect were no longer connecting to our Foritgate<\/p>

If using VDOM use\u00a0<\/p>

#conf Global<\/p>

#diagnose sys top<\/p>

Check for Free Memory Usage( Should not be over 80% )\u00a0<\/p>

Enable Debug for VPN<\/p>

#dia debug en
#dia debug reset
#dia debug application sslvpn -1<\/p>

Then Connect VPN , and check for logs for that user<\/p>

Found :\u00a0<\/p>

\u00a0“no more addresses” fortigate<\/strong><\/p>

#diagnose debug disable<\/em><\/p>

#exec vpn sslvpn list<\/p>

If using VDOM Use this before<\/p>

#conf vdom<\/p>

#edit Vdom Name\u00a0<\/p>

Users where getting 4 Address in the SSL VPN Sessions instead of one which was filling up the DHCP List<\/p>

#fnsysctl ps<\/p>

find the PID of sslvpnd<\/p>

#run diag sys kill 11\u00a0<pid><\/p>

VPN Service will restart Automatically.<\/p>

 <\/p>

If FortiClient fails as the following stages, the likely cause is as follows:<\/p>

\u00a0<\/div>

  • 10% \u2013 Local Network\/PC issue<\/p><\/li>

  • 40% \u2013 Application or the Fortigate causing the error, occasionally caused by the local machines\/network setup<\/p><\/li>

  • 45% \u2013 MultiFactor Authentication<\/p><\/li>

  • 80% \u2013 Username\/Password issue<\/p><\/li>

  • 98% \u2013 corruption of services\/often resolved by reinstalling the client on the laptop.<\/p><\/li><\/ul>

     <\/p>

    Client Logging<\/strong><\/p>

    You will want to:<\/p>

    1. Clear the logs if you have any there.<\/li>
    2. Set the\u00a0Log Level<\/code>\u00a0to\u00a0Debug<\/code>\u00a0to ensure the highest verbosity. (Make sure to disabled after troubleshooting)<\/li>
    3. Run the attempt, and then\u00a0Export logs<\/code><\/li><\/ol>

       <\/p>

       <\/p>

      Client: Access Sydney<\/p>

      Device: Fortigate 60E<\/p>

      FortiOS ver 6.4.3<\/p>

      \u00a0<\/b><\/p>

      Symptoms:<\/b><\/p>

      • User connects to VPN but Forticlient errors, Unable to receive SSL VPN tunnel IP address -30
        \"\"\u00a0

        <\/li>
      • Checked the Fortigate, no VPN users connected<\/li>
      • 20 free IP address in the VPN IP Pool


        <\/li><\/ul>

        Troubleshooting:<\/b><\/p>

        • Enabled debugging, reattempted connection and found error relating to IP allocation failure<\/li><\/ul>

          \"\"<\/p>

          \u00a0<\/p>

          \u00a0<\/p>

          Quick fix:<\/b>\u00a0killed the sslvpnd process (this will terminate all VPN connections)<\/p>

          \u00a0<\/p>

          Found that a later version of FortiOS has fixed this bug:<\/p>

          \"\"<\/p>

          \u00a0<\/p>

          \u00a0<\/p>","protected":false},"excerpt":{"rendered":"

          Users who could connect were no longer connecting to our ForitgateIf using VDOM use\u00a0#conf Global#diagnose sys topCheck for Free Memory Usage( Should not be over 80% )\u00a0Enable […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[3780,1392,1391,1199,1393,1251,1250,850,3779,1390],"class_list":["post-1938","post","type-post","status-publish","format-standard","hentry","category-random","tag-3780","tag-5-2-4","tag-debug","tag-dhcp","tag-forticlient","tag-fortigate","tag-fortinet","tag-ssl","tag-unable-to-receive-ssl-vpn-tunnel-ip-address","tag-vdom"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t