The FortiClient(EMS) not working occasionally if Windows got some updates.

[Ali84]

Hi All, 

I realized that if Windows gets some updates, FortiClient EMS is not working correctly occasionally. 

I'm wondering whether anyone knows about this. Is there any way to work around it? ... 

I appreciate any help you can provide. 

[Anthony_E]

Hello Ali84,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

Thanks,

[srajeswaran]

Hi Ali84, Could you please share more details on the issue. When you say Forticlient EMS not working, do you mean you are not able to open the client, is it continuosuly crashing or the features are not working.

Is this observed across multiple machines? Do you see any specific error?

[Ali84]

On the Fortigate, under Fortiview SSL-VPN monitor, the Bytes column showed "Bytes Received" as 0, with "Bytes Sent" as nonzero.

The VPN connection on the Forticlient connected without error, but not traffic was passing.

Nothing was being blocked by the firewall policies for the client

 

[srajeswaran]

I see the similar issue reported by other users as well. Could you please open a support ticket to get this investigated further.

https://community.fortinet.com/t5/Support-Forum/forticlient-vpn-Error-find-interface-for-local-gwy-0...

[srajeswaran]

I was checking further on "WSAEnumNetworkEvents FD_CLOSE (10053)" from you debug, I can see that this could be caused by any third party application (especiall AV or VPN app) installed on the machine. 

https://community.fortinet.com/t5/FortiClient/Technical-Tip-Interpreting-WSAGetLastError-in-FortiCli...

https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2

Do you have any other VPN clients/AVs installed on this machine? I think it will be worth trying to uninstall them and check.

[btan]

Hello,

This symptom looks like what mentioned in below KB:
https://community.fortinet.com/t5/FortiClient/Troubleshooting-Tip-VPN-SSL-connected-but-no-IP-addres...
Perhaps KB2693643 is the root cause.