I was seeing this error with 4.2.4b but having gone back to 4.1 it has disappeared. I too was only writing, not streaming at the same time.Yes, but even when "*we*" think we are only writing, windows itself is often doing "reads" to keep itself in sync for folder listings, etc.
I don't think I ever saw it in 4.1 either. Probably should try older version of smbd and see if problem goes away. (It could be samba, it could be the networking itself, it could be in the OS. Need to start isolating the cause one thing at a time)
The version of smbd that has the disconnect bug is 3.0.25b
To tell if you have the buggy version, login via telnet and type:/usr/sbin/smbd -V
The working version is 3.0.24.
I sure the buggy version of smbd is in unRaid 4.2
and think it might even be in 4.1
. Edit: unRaid 4.1 uses version 3.0.24 of smbd
I've now got a copy of smbd 3.0.24 on my flash drive. I've also added a line to my "go" script to copy
it to /usr/sbin/smbd just prior to emhttp being invoked.
This will fix the disconnect bug for me until Tom can get a newer version in a new release of unRaid.
cp /boot/smbd /usr/sbin/smbd; chmod +x /usr/sbin/smbd
easiest way to get the older version is to boot up an older release of unRaid and then copy the file to the flash drive. cp /usr/sbin/smbd /boot/smbd
Then, boot up the newer release and the file should be there for your use. I got my older (version) copy of smbd from unRaid 4.0beta9 since I had it on my alternate flash drive.