[RPi] Can't connect to NAS

    our NAS got destroyed in a recent move. so i built a new one and ran the same OS on it, same IP, same accounts, same mount points, everything (the joy of OS on a stick). but the RPi LibreElec Kodi now errors out: 'cannot connect to server'. WTH!?

    i can SSH in without issue to both machines. the RPi can ping AND SSH into the NAS... but the UI... nope. i can't even remove or edit the library to try and delete and restart sorta thing. the Wiki is... less than helpful , particularly for a console jockey like me. i would appreciate some advice on where to find the files to edit manually to either reset this silly thing or somehow get it to connect back to the new NAS. it makes no sense. /shrug

    The only thing that comes to mind is SMB versions? .. i.e. old NAS was configured for SMBv1 which requires the Kodi SMB client on the RPi to be configured for min/max SMBv1 (else it connects at SMBv2 and cannot downgrade the connection to SMBv1) and new NAS has defaulted to SMBv2/3 thus prevening the Kodi SMB client trying to use min/max SMBv1 from being able to connect.

    If that's not the right blind guess, as a minimum you'll need to divulge what protocol is used by Kodi.

    i will look into that. i thought that setting the min/max would span the versions. i know SMBv1 is generally dead in the water, but some working systems still use it. i never thought that i had to dial it in that way. but i'll give it a whirl. thank you for answering so quickly, particularly on Christmas. :)

    The gotcha with SMB is that the default connect version in smbclient is SMBv2, and while the client can/will upgrade to better SMBv3 on successful connection it has no logic to attempt a new connection with SMBv1 on an unsuccessful SMBv2 attempt; the connection attempt simply fails. This was an intentional move (some 20 years ago) to herd people away from insecure SMBv1 and while there is logic to how it works, the behaviour can catch people out sometimes.

    two gotchas: one was the SMB version settings (thank you for that). the other... *sigh* i mistyped the IP when i blew it away and rebuilt it. i feel like an idiot, but its a solid lesson that no matter how seasoned you are, you will make stupid mistakes when you are tired and frustrated. thanks for the help. i'm back up and running... sorta. now i have to reconfigure the UI from default. :P