iprope_in_check

[connect555]

Hi, i' ve tried to connect a Network Device (a Switch) with IP 172.16.100.254 to our FortiGate 80C WAN2 with IP 172.16.100.250. When I ping the Switch from the FortiGate, anything is allright and I get an answer in <1ms. The problem is the other direction. I can' t ping the FortiGate from Switch. (Ping Access is activated in the Interface Settings) The output from ' diagnose debug flow' from ' ping 172.16.100.250' id=13 trace_id=791 msg=" vd-root received a packet(proto=1, 172.16.100.254:1430->172.16.100.250:8) from WAN2." id=13 trace_id=791 msg=" allocate a new session-000033a3" id=13 trace_id=791 msg=" iprope_in_check() check failed, drop" the output from ' diagnose sniffer packet ' wan2' ' : 12.665446 172.16.100.254 -> 172.16.100.250: icmp: echo request Has anyone an idea why I can' t ping the FG? What is an iprobe_in_check?

[FortiRack_Eric]

It means that the ping access on the interface is not enabled and if it is then all the admin' s IP ranges together (allow-hosts) don' t allow the interface to be pinged from that IP address