>но по прошествии случайного кол-ва времени (часы, минуты) на клиенте сообщение:
>Network device no longer exists reading drive G: На
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q988...
указано, что "The symptoms of a timeout-related data transfer failure vary depending on the type of process running on the workstation. For example, if you are copying files to/from the server at the MS-DOS command line, one of the following errors may occur:
NET805: Network device no longer exists reading drive H
Abort, Retry, Fail?"
и "You need to remember that if you have a slow link between redirector and server you must increase this "session timeout" on both the redirector (workstation, client) side and the server side. On the redirector side, the session timeout is exposed by means of the sesstimeout parameter."Remember that when you increase this timeout on the redirector, you also normally need to increase the related timeout on the server side. The server side session timeout is exposed by means of serverheuristic 15. The documentation describes this heuristic as "oplock timeout," but does not include the fact that this same heuristic is also used to set LANMAN.INI file [workstation] sectionthe "session timeout." The heuristic values documented are correct for the oplock timeout, but do not correspond to the values used for the session timeout."
т.е. получается на клиентской DOS-машине надо отредактить файл LANMAN.INI [workstation] секция, параметр SESSTIMEOUT, а какой параметр необходимо изменить в smb.conf для server side session timeout?
