Session timeout with the SQL server

My users connect via Remote Connection to the SQL server, and after a period of inactivity the connection becomes partly disconnected. They can poll data from the server, but after setting up a record update in their client, when they try to save the update they are unable to do so until they reconnect.

You can imagine how maddening this is to the average end user trying to process something for a customer, thinking they are still connected right up until the record save.

This seems kind of buggy. But can anyone point me to a configuration setting that might clear this up? Or any answers?