![]() Thanks a lot in advance! Let me know if any information is missing. Installed SMB v1 (not enabled on NAS, but tried anyway) Trying a different network connection on the PCĬhanged the hostname of both the NAS and the PCĬhanged the IP address of both the NAS and the PC version 0.9.1 : mucommander get the shares list, but doesnt show the content of the share (empty) if I clic on that share. I have tried various troubleshooting steps such as: To switch between the volumes or servers, click on the name, and it will list all the drives, network shares, Bonjour services, and access to FTP, SFTP, SMB, NFS, HTTP, etc. Next, as we have not yet added a storage provider we will are asked to select a storage system to use, we will choose CIFS: This will invoke the CIFS wizard: Once we fill in the relevant authentication details for the CIFS share the File Fabric will connect and ‘smart index’ the file metadata (no files. When I try to connect to an SMB share on this server, the behaviour of mucommander depends of the version : version 0.9.0 : I get the authentication failure despite the credentials are. Unlike mount. Context : Samba 4.5.1 ActiveDirectory on Debian Jessie server. Intel(R) Wi-Fi 6 AX200 160Mhz network adapter 1 Answer Sorted by: 9 150 Yes, but it comes at a price. 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. The problem with the package on the NAS was eventually solved and the NAS has been working properly for about five weeks now. 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. |