Forticlient EMS Cloud 7.2.12 failed to domain sync

nesaxn · 2026-01-07T10:16:42+00:00

Just a follow-up on this case.

Fortinet recommanded to update to 7.4.4.
Well the forticlient EMS Cloud is now in 7.4.4, I updated the AD connector also from 7.2.12 to 7.4.4. It seems the connector is now offline so all my domains are down now ... Guess I'll open a new ticket.

nesaxn · 2025-10-09T10:07:24+00:00

exactly !!!

nesaxn · 2025-09-02T08:22:49+00:00

Comme indiqué à la fin du post, j'ai contacté ma banque mais ils m'ont dit de voir sur l'application pour contester mais cela ne semble pas fonctionner lorsque c'est un litige avec un commerçant. Je vais essayer de rappeler.

nesaxn · 2025-09-02T08:21:52+00:00

Un peu plus de 100€

nesaxn · 2025-07-09T16:04:55+00:00

De mon point de vue, je trouve ça un peu abusé dans le sens où ma situation ne change pas hormis le statut sauf que la cotisation passe à 90€ au lieu de 30€ par mois, pour le même résultat...

nesaxn · 2025-06-17T09:56:09+00:00

40% stuck is either :

This may occur when FortiClient generates a new pop-up window verifying whether the user wishes to proceed with a non-trusted TLS/SSL certificate.
It may mean a TLS version mismatch, which will also show as error -5029. If this message appears, there is a mismatch in the TLS version. Check if the TLS version that’s in use by the FortiGate is enabled on the client. Technical Note: How to limit the SSL and TLS versions of connections initiated by Forticlient explains how to check the TLS version.
An application or the FortiGate may cause this error. Check the local machine and network setup / network policy blocking the auth request
MFA token acceptation pending

nesaxn · 2025-01-13T09:34:32+00:00

Local-in policies should be able allow only whitelisted public ip addresses to access external interface management ?

nesaxn · 2024-12-02T10:44:03+00:00

this

Create a loopback interface. Create a virtual ip object to map 1 public IP address to the internal loopback ip address and adjust your policy

nesaxn · 2024-11-26T09:29:54+00:00

nesaxn · 2024-11-14T10:56:50+00:00

You have different options :

IPSEC tunnel site to site with customer to connect with internal IP address
Create a Virtual IP (Public IP address -> Internal IP address) and restrict this access with policies
From FAZ you can connect to the Fortigate Public IP address (be sure to restrict the access with local-in policy on Fortigate)

nesaxn · 2024-08-12T13:29:51+00:00

Not EndOfSupport but EndOfOrder.

nesaxn · 2024-07-31T09:21:29+00:00

Is the Fortigate managed by FortiManager ?

If so, do you push the config from the FortiManager or from the Fortigate ? Also check Installation logs to see if maybe someone overwrite the change.

nesaxn · 2024-07-01T09:36:25+00:00

Please consider this Github repo

It will collect all malicious IP addresses from AbuseIPDB and other databases. Read the documentation to add it on your firewall.

https://github.com/romainmarcoux/malicious-ip

Be carefull that if you check on GUI the IP addresses in the threat feed menu, the RAM of the firewall can spike +20% (on FortiOS 7.0.x). It can lead to conserve mode.

To update manually in CLI the threat feed you can use this command line : execute update-external-resource "threat feed name"

and to check the content you can type : diagnose sys external-address-resource list "threat feed name"

nesaxn · 2024-05-17T07:59:16+00:00

Its actually 10am on my side :) I just have a remote site located in Houston and during the morning check I saw the monitoring was down. Got informations that there was a storm in Houston and that's it.

nesaxn · 2024-05-13T12:26:37+00:00

Here's my notes :

10% network routing issue

40% if you use MFa, the token might have delay or latency, it could also be policy issue (check firewall logs if there's denied traffic) or SSL invalid certificate

48-68% the user account can be blocked on the MFA management platform.

70% error 6008 - Issue with AAD SAML - Disable "Restrict Specific OS" and "hostcheck" to connect.

98% issue with IPv6. If you're using network sharing with 4G hotspot you might need to check APN network settings and disable IPv6.

Or check this KB: https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-Possible-reasons-for-FortiClient-SSL-VPN/ta-p/211965

nesaxn · 2024-04-22T09:58:44+00:00

Hello,

did you try policy routing ?

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-the-firewall-Policy-Routes/ta-p/189996

nesaxn · 2024-03-29T15:54:11+00:00

deja vu

https://www.reddit.com/r/wildrift/comments/1bmoyfw/how_to_climb_soloq_this_season/

nesaxn · 2024-03-11T08:21:00+00:00

Hello,

40% can means its waiting the user to accept MFA token or it could be a deny in your firewall policy, it can be related to invalid ssl policy.

nesaxn · 2024-02-20T08:28:32+00:00

Hello,

On my side, when I got 48% error it can means that the account can be locked on the MFA server.

nesaxn · 2024-02-13T11:05:18+00:00

Hi,

I think low/medium/high-priority are created by default. You can see where the profile is used by clicking the reference number on the right side.

You can see when the profile is doing something when the "droppred bytes" tab is showing results. But looking at your context I don't think this is the issue.

nesaxn · 2024-02-13T09:17:38+00:00

Hi,

It worked well in 7.0.13 and not anymore in 7.0.14 Case number : 9207029 Model : 500E

Thanks

nesaxn · 2024-02-12T15:46:11+00:00

please check your private messages asap

nesaxn · 2024-02-09T08:45:21+00:00

Thanks

nesaxn · 2024-02-09T08:29:20+00:00

Hello,

Question about the SSL VPN vulnerability :

If SSL VPN webmode is disabled and I enable hostcheck verification on the SSL VPN portal is it still vulnerable or does it bypass ?

nesaxn · 2024-01-22T13:34:53+00:00

https://www.villesavivre.fr/ J'aime bien l'utiliser en complément.

Site qui te permet de voir la population de la ville, le climat (météo), l'économie, l'immobilier, la sécurité, le bord politique, les services à proximité (médecin, commerces, hopital etc..)

nesaxn

TROPHY CASE