Author Topic: SMB2 enabled on LS-WVL (LS-PRO-DUO) but drops connections every 1-3 hours  (Read 100 times)

pkiff

  • Calf
  • *
  • Posts: 4
So I updated from SMB1 to SMB2 on my LS-WVL (LS-PRO-DUO) LinkStation using the instructions here:
http://forums.buffalotech.com/index.php?topic=24630.0

And I can connect just fine from both Windows 7 and Windows 10 boxes. I can map a folder to a drive letter. I can connect via network name or via IP address.

However, my connection gets dropped from Windows boxes after 1-3 hours or so. When it disconnects, I get an error in Windows Explorer that says "Wrong parameter". Note that when this connection is broken, it is still possible for me to connect to the LinkStation by logging into the admin UI via the IP address in my browser. It is also possible to access files made available via the DLNA server. I just can't connect via the mapped network drive any longer.

If I log off then log back on then the connection is re-established.

Is this a problem with my SMB2 config on the LinkStation?

Or the network settings on my computers connecting to it?

It seems like it must be some kind of time-out, but I came across a dizzying array of different settings that might affect this, so I'm hoping to narrow down my troubleshooting with the help of someone who knows more about Samba or about the limitations of SMB upgrades on devices like these ones that don't officially support SMB2 even though it is available in the software provided. Here are some pages that I'm trying to search through for an answer:
https://blogs.msdn.microsoft.com/openspecification/2013/03/19/cifs-and-smb-timeouts-in-windows/
https://blogs.msdn.microsoft.com/openspecification/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows/

Additional info:
Firmware: 1.74
2 x 2TB drives configured as RAID 1
For all mapped connections I use separate credentials with a username and password to access the drive that are saved as custom credentials when I set up the mapping, and that are stored in the LinkStation under users.
« Last Edit: October 05, 2018, 09:57:17 am by pkiff »

pkiff

  • Calf
  • *
  • Posts: 4
Is this a problem with my SMB2 config on the LinkStation?
I did some further troubleshooting and disabled all authentication on the share folder on the LinkStation, and since then there have been no issues or dropouts for any device. I think that means the problem is pretty much for sure a config or implementation issue with SMB2 on the LinkStation side.

It would still be nice to know if it can be fixed by a simple config tweak of the smb.sh file on the Linkstation. But as this is a personal local network primarily for media files, I can probably live with leaving it wide open.

pkiff

  • Calf
  • *
  • Posts: 4
I spoke too soon regarding dropouts in the new config. The dropouts now take much longer to occur, and they don't seem to occur if the drive is in the middle of some kind of activity. So, for example, if you are copying files from one drive to another, and it takes 12 hours, there will not be a dropout. But if you let is sit there for 12 hours without any activity, then when you want to do something, you may get an error.