12-06-2018, 09:33 PM
(12-06-2018, 05:03 PM)TheOldPresbyope Wrote:(12-06-2018, 02:48 PM)Zigzag Wrote: Bingo!! I've just changed the first part of the mount flag from 'vers=1.0' to 'vers=3.0' and it now works if I use the IP address for the NAS rather than its network name. Yippee!! Thanks for your help Tim.
Curious. Your problem forced me to boot into Win10 ("the other OS" in my house). I set up a share on my Win10 host. Smb-GetConnection reports the same "3.1.1" dialect.
I was able to mount the share in moOde without changing from the default "vers=1.0" !?!
---
As an aside-
The error messages in the moode.log output you posted showed that moOde couldn't reach your server by hostname. When that happens the mount process quits.Reporting the moode.log output you got trying to access the share by IP address would have been informative.
Chasing down SMB connection problems is a real challenge but I remember the bad old days chasing down NFS connection problems at work where the network administrators always seemed too busy to return calls. Yuck.
Regards,
Kent
Interesting Kent, thanks for your post.
I've done a bit more digging into this issue. You may recall me saying in an earlier post to Tim that I had configured the NAS so that the minimum SMB protocol was set to: ‘SMB2 and Large MTU’. As a test I changed that to 'SMB1' and after the SMB service restarted I went back into MoOde and tried creating another NAS source, like you, leaving the mount flag unchanged at the default value of 1, and low and behold that test connection worked! Albeit, as before only when using an IP address for my NAS - some code clearly dislikes my NAS having 'NAS' as a network name.
Incidentally, as the SMB1 protocol is now considered to be outdated and insecure, I've since changed the minimum SMB protocol back to ‘SMB2 and Large MTU' and going forwards, if needs be, personally I will continue to set the mount flag in MoOde to '3.0