Hello. I have a question to FortiClient EMS and registration of
endpoints/clients to FortiEMS-Server which is public reachable through
port 8013. I have configured that clients need an invitation code and
afterwards need to autenticate with ldap user...
Hello. We want to change our EMS-Server to be reachable from Public and
not only from internal network. At the moment users connect to an
internal FQDN-Name while on internal network or connected via VPN. When
changing the FQDN name of EMS-Server to ...
Hello. I want to let "normal" users with the role "Standard User" to add
secrets as their favorites. As you can see in the screenshot the option
at a normal user is greyed out with that role. Admin users can add
secrets to their favorites. Can somebo...
Hello. I want to setup a dial up ipsec vpn tunnel from FortiClient to
FortiGate. The tunnel is working with transport mode "udp" and port
"500". When I change the transport mode in phase1-settings to "tcp" or
"auto" and than use "tcp" in FortiClient,...
Hello. In "Advanced Settings" -> "Syslog Servers" you can set an ip
address so send SSO Agent logs via syslog to a syslog server. Is there
any option so select the message severity to send via syslog? At the
moment the agent sending all debug and inf...
One question to "EMS Server List":At the moment I have disabled
"Configure EMS Server List". Does it mean clients can only connect to
the current FQDN which is in "Use FQDN"? Activating this option will
give me the opotunity to connect to more than o...
Yes that is exactly the way I wanted to do, to create the same FQDN
which resolves internal to an internal ip and external to an external
ip. If I understand you correct - the best way to do this is: 1) Change
FQDN Name in EMS Settings2) EMS Clients ...
I send you an email with case number. When reinstalling 7.4.3 with
previous removal of FortiClient with FortiClient-Remover-Tool, than it
also works. But these adapters where coming with some previous version
of FortiClient. We had issues with client...
I opened a ticket and there was nothing about a bug... they just
confirmed that it is a solution to solve the problem. Seems this issue
is present in many forticlient versions.. maybe a "normal" behaviour in
some cirumstances when you update your for...
For me the solution was to check network adapters from Fortinet in
"Device-Manager". There were Fortinet Adapters with #2 or #3 at the end.
Delete them, afterwars it started to work.
