Hello,I created the following rule to allow an IPSec client network aka
EMS_IKEv1_F_NB [198.18.27.0/24] to access Intranet aka TRK3
[192.168.0.0/16]. Nevertheless the clients is blocked by the implicit
deny rule.When I try to check the policy using t...
Hello,I set up IPSec connections for roaming clients with
split-tunneling. Although the connections succeed phase 2 and R_U_THERE
packets do cross the tunnel, there is no packet flow between client and
the Fortigate. Neither one can ping the other th...
Hello,I have problems to authenticate AD users in a newly installed
Forticlient (Win11) connected to FortiClient EMS cloud 7.2.4. In EMS
cloud the logfile reads:EMS ServiceRegistration attempt by Endpoint []
was denied due to LDAP authentication fail...
Hello, I fail in connecting a FG-200F v7.2.4 to FortiClient EMS cloud.
In "Fabric Connectors" -> "Connection status" it reads: FortiGate not
authorized, but in FortiClient EMS cloud neither the Authorization
pop-up is displayed nor occurs the device ...
Hello,I´d like to setup #FortiClient FortiEMS Cloud AD-connector. But
the documentation lacks the information where to find the Where to find
the Connector
UIDhttps://docs.fortinet.com/document/forticlient/7.2.2/ems-administration-guide/787816/ad-con...
Hello @AEK ,we have no other client working with policy.No, we have no
DoS policy,No, we have no other policies for traffic from 198.18.27.0/24
best regardsMartin
Hello@dbhavsar , thank You for Your reply. I will post the output within
the next days. I have to setup my own client for a tunnel lab, because
my colleague quit already for the weekend. best regardsMartin
Hello@sakuraju , that is right. because 456.456.456.456 is an external
destination which is not allowed in that rule.But the response DNS
response does not arrive at the client. Although I seeid=65308
trace_id=59 func=_do_ipsecdev_hard_start_xmit lin...
