Windows cifs timeout

Fly-Tech Sonora. Replace Attachment. Add link Text to display: Where should this link go? Add Cancel. Insert code. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. This website uses cookies. By clicking Accept, you consent to the use of cookies.

Click Here to learn more about how we use cookies. Start a New Post. Please I need you assistance to get this resolved asap. Thanks in advance. All forum topics Previous Topic Next Topic. This discounts any TimeZone settings. They should be close. If they are not, set your time, setup a NTP server. When copying files or backing up files to a CIFS share hosted from a CloudArray; the operation performs fine for small backups or general files.

This, however, has several limitations. What is Samba? After checking the configuration files for the SAMBA shares; we found that the default settings for the timeout of idle connections that are no longer in use are set to 10 minutes. This forces the Linux machine to then wait 10 minutes before it will close the connections. The client machines in most cases will hit errors with a second timeout due to the sesstimeout detailed in the article below.

To perform this workaround; this would first have to be configured from the root Shell of the CloudArray.