I have an odd situation where I have 2 separate shared drives on a TS-212US. Some time ago I had a shared folder from each drive mapped to a Windows 11 machine over the network. One of them got disconnected and I couldn’t reconnect. Using Qfinder, I can see the NAS. However, when I am in Windows and try to map the folder or even see the NAS on the network, it’s not visible. SMB 1.0 is enabled and the currently mapped folder would not be accessible if it wasn’t. Hoping someone can provide some insight as to how to get this working again.
Login to the NAS and see if the disk shows up.
With single disks, a catastrophic failure of one disk would explain the disappearance of a share.
Thanks - I should have mentioned that the other disk and folder shows up. Fully accessible, and I was able to copy some files across the disks. This was just a storage drive to drop extra files so RAID and protection wasn’t important. The issue here was why the second folder on the second disk is no longer able to be mapped and, more importantly, why the entire NAS and its IP is inacessible from Windows - although the map works fine.
Can you please describe the steps you took to re-enable SMB1 support in Win11?
Are you able to use a later SMB version?
If your NAS is setup with single drives, then the failure of one drive will result in the loss of the files on that drive. If you cannot reach the WebGUI of the NAS, maybe the drive with the system volume failed (yes, NAS drives hold more than just your data, they also hold the NAS OS)
Can you access the NAS via SSH?
In terms of SSH, why SMB1 ? You can enable SMB 2.1 or higher with CAT1 units.
Could you please run a disk check first to see the current health status of your drives? Thanks!
I didn’t re-enable SMB. I noticed it was already enabled looking at local administrator’s rights in Win 11.
SMART says GOOD.
I’m in the WebGUI, no issues. This model NAS is very slow so I use it just for tossing files on it as backup. I’m probably going to remove the large drives and just put in two small drives to keep it lean.
Oddly enough, suddenly I’m able to reconnect. I had to type in the direct pathway into the browse using the IP address and then the shared folder name - and that connected. Mapping and browsing doesn’t work. The drive does not show up in the network neighborhood and I can only see Twonky running. It’s very strange.