| Description | This article describes the issue with assigning FortiToken to a user and steps to verify if 'Timeout occurred! No data rcvd after 240 seconds' occurs in FortiToken debug. |
| Scope | FortiGate, FortiToken. |
| Solution |
While assigning FortiToken to Users, 'Some unknown error!' appears.
To resolve the issue of being unable to assign FortiToken to users, follow these steps:
Step 1: Check the FortiGate configuration and ensure that the FortiToken is properly configured and licensed.
Step 2: Verify the reachability to the DNS server. If DNS is unreachable, refer to the steps in the article Technical Tip: How to solve 'unreachable' or high latency issue when using FortiGuard DNS servers.
Step 3: Verify and ensure the reachability to FortiGuard and these servers:
exec ping fds1.fortinet.com
Step 4: Collect FortiToken Debug logs:
diagnose debug dis
diagnose debug reset
diagnose debug console time en
diagnose debug app forticldd 255
diagnose fortitoken debug enable
diagnose debug enable
diagnose debug info
To Stop Debugging:
diagnose debug disable
diagnose debug reset
If the following error is received:
2025-05-15 17:24:37 [3117] fds_handle_request: Received cmd 116 from pid-8172, len 0
2025-05-15 17:24:37 [454] fds_send_reply: Sending 8 bytes data. 2025-05-15 17:25:03 __read_some_more[343]:[__read_some_more:343] Timeout occurred! No data rcvd after 240 seconds. 2025-05-15 17:25:03 ftm_fc_comm_recv_response[464]:recv packet error 2025-05-15 17:25:03 ftm_fc_command[555]:receive from forticare error [-333] 2025-05-15 17:25:07 [3117] fds_handle_request: Received cmd 116 from pid-8154, len 0 2025-05-15 17:25:07 [454] fds_send_reply: Sending 8 bytes data. 2025-05-15 17:25:07 [3117] fds_handle_request: Received cmd 116 from pid-8154, len 0 2025-05-15 17:25:07 [454] fds_send_reply: Sending 8 bytes data.
Try adjusting the MTU value of the WAN interface, as described in the article Technical Tip: How to adjust the Maximum Transmission Unit (MTU).
config system interface
edit "<wan_interface>"
set vdom "root"
set mtu-override enable
set mtu 1300
next
end
If the issue persists, collect debug logs and contact FortiGate support for further assistance. |
