None of the above have worked - I still receive the same error. Installed SMB v1 (not enabled on NAS, but tried anyway).You should see and the resources mentioned in it, and try to remove any dependencies to SMB1 if at all possible. Changed the IP address of both the NAS and the PC As a result, SMB1 is now deprecated and on its way out.7 From the Downloads folder, double-click the file to begin the download. Check SMB 1. dmg file downloads to your Downloads folder. Changed the hostname of both the NAS and the PC Select Programs > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support. Trying a different network connection on the PC.network resets on the Windows 10 machine.I have tried various troubleshooting steps such as: First thing: taking a quick look at bcmount.sh, it looks like it's calling /usr/lib/beyondcompare/bcmount64 smb://192.168.5.40 (for example) to do the mount, and then the 'not a member of the FUSE group' message I mentioned is printed after it fails. Intel(R) Wi-Fi 6 AX200 160Mhz network adapter Synology DiskStation DS420+ (setup to support SMB2, SMB2 and large MTU, SMB3) When the problem started I did not do any updates or setting changes on the Windows 10 machine, the router or NAS.ĭoes anyone have any idea how I can reset that, without reinstalling the complete machine? I suspect that the Windows 10 machine has mixed something up and the problem is with the PC/ Windows' SMB service. Therefore I do not think it has anything to do with my network setup, but really with that specific Windows 10 machine.Īlso from other PCs, media players or phones in the network, I can use the SMB shares on the NAS just fine (with the same user). I can use SMB on this machine when I install a third party client (muCommander in this case). Also I cannot access SMB shares on other machines than the NAS. Only when I try to use Windows explorer (or play some music from the NAS via software that had files in the history) it eventually 'times out'. The error I get (after waiting for a long time) is:įrom the same machine I can ping the NAS, the SMB ports are open, I can browse the UI via a browser, connect to the NAS via FTP. However, the network share on the NAS is still not accessible from the Windows 10 PC, but can be accessed from other Windows 10 and 11 machines on the network. Now you can mount the WebDAV share using the following commands in bold. The problem with the package on the NAS was eventually solved and the NAS has been working properly for about five weeks now. From the windows side, we are able to connect to our filer via FTP, CIFS. Also, from my Windows 10 PC, that used these shares for years, the Explorer was taking a long time to load and eventually gave the message "Windows cannot access \192.168.1.3\Photo_archive". Recently, a package on the NAS was causing a slow performance, with the interface loading slowly and streaming files not working. For years I have a Synology NAS running in my network for various uses and it is accessed by multiple devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |