Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
New Contributor

Fortinet Client VPN v7.2.3.0522 cannot access remote file server

Hi Community,
I have an user on Mac Book Air OS 14.3 with Forticlient VPN v7.2.3.0522. The issue is, the VPN will connect with IP-Sec however cannot ping or access a remote file server.
Interestingly the same user with an old Windows 10 Pro laptop with the same credentials can connect on VPN, and can access the remote file server that is mapped as a network drive.
Both the VPN clients on Mac and Windows laptop have identical configurations.
Does anyone have similar issue on the Mac that cannot access a remote file server?


Hi @michael_chan ,
Are you folders mounted with FQDN name?


More information on mapping a network drive in Mac:

Some times the IPv6 can cause issues. Try to disable it from Wi-fi or LAN interface of the Mac device. 

If you have found a solution, please like and accept it to make it easily accessible for others.

Hi dbu,
The Mac is operating on IP v4. The IPv6 is not in use.
Interestingly when the Mac connects to our firewall, it can ping one of the servers on, however cannot ping another server on

I tried to mount the folder by IP address ( and also by FQDN, it just timed prompt the server does not exist.

I tried to mount folder on, the server responded for credentials.

Just not sure why the cannot connect.


Is there routing in place to reach server ? 



If you have found a solution, please like and accept it to make it easily accessible for others.

When we are in office, using the LAN network, is accessible.
The user on Windows laptop and VPN can access remotely.
We setup the Mac in the same way, same configuration, just cannot access while remotely.


Hi dbu,
Are you able to give further troubleshooting tips on how to resolve the issue?


Hi michael, 
Have you tested the same user credentials both on windows and mac?
Check also the mac routing table (netstat -nr) if there was an entry for subnet.


We use the same credentials on both Windows and Mac.
The Windows laptop has no issue on accessing: server
I done a "netstat -nr" on the Mac, please view:


Destination Gateway Flags Netif Expire
default UGScg en0
default UGScIg en0
10 UGSc utun4
127 UCS lo0 UH lo0
169.254 link#12 UCS en0 ! UGSc utun4
172.17 UGSc utun4
192.168.0/16 UGSc utun4
192.168.31 link#12 UCS en0 ! link#12 UCS en0 ! 64:64:4a:3e:62:ed UHLWIir en0 1200 link#12 UCS en0 ! a2:d2:41:d3:2c:46 UHLWIi en0 1168 ff:ff:ff:ff:ff:ff UHLWbI en0 ! UHr utun4 link#19 UCS utun4 UGSc en0
224.0.0/4 link#19 UmCS utun4
224.0.0/4 link#12 UmCSI en0 ! 1:0:5e:0:0:fb UHmLWI en0 link#19 UCS utun4 link#12 UCSI en0 !


Please advise on this.


Hi @michael_chan,


I would suggest running debug flow and replicate the issue to see if the traffic is being dropped or not. Please refer to


Example: (replace x.x.x.x with remote file server IP and try to ping it from the VPN client)


di deb disable
di deb res
diagnose debug flow filter clear
di deb flow filter proto 1
di deb flow filter addr x.x.x.x
diagnose debug flow show function-name enable
di deb flow show iprope en
diagnose debug console timestamp enable
diagnose debug flow trace start 500
diagnose debug enable


Run 'di deb dis' to disable the debug. 



New Contributor

I've experienced a similar issue with Fortinet Client VPN on Mac. Ensure that the firewall settings on the Mac aren't blocking the VPN connection. Also, double-check routing and DNS configurations. If the problem persists, contacting Fortinet Americas Paint support might provide specific insights into Mac compatibility issues. Good luck troubleshooting, and I hope you get it resolved soon.

Top Kudoed Authors