The client is supposed to send the host a "tickle" if there has been no other network activity to the host for 60 seconds.
If the host doesn't hear from a client for 125 seconds and doesn't have anything to send to the client, it will disconnect the client since this means the client has failed to send two "tickle" messages.
As for the errors: FileMaker Server will log a message like one of the following in the Access.log file when a client connection fails, assuming Client Access logging is enabled:
[Client Name, etc] no longer responding; connection closed. (10)
[Client Name, etc] no longer responding; connection closed. (51)
The (10) indicates that the 125 second timeout elapsed as described above. The (51) indicates that the TCP connection failed when Server tried to send something to the client.
A frequent cause of this is faulty hardware, including cables, NIC cards, etc. Is this occurring on multiple machines or just one workstation?
Steven H. Blackwell
Platinum Member Emeritus, FileMaker Business Alliance
Platinum Member, FileMaker Business Alliance (2007-2011)
Partner Member, FileMaker Solutions Alliance (1998-2007)
Partner Member, Claris Solutions Alliance (1997)
FileMaker Certified Developer 7|8|9|10|11|12
FileMaker Authorized Trainer 9|10|11|12
_ _ ____________________________ _ _