cross-posted from: https://lemmy.world/post/15050323

Cannot connect to my NAS after installing KUbuntu 24.04 LTS

I was first on KUbuntu 22.04 LTS and was able to connect to my router’s attached USB storage drive by adding client min protocol = NT1 to the smb.conf file within user/share/samba. My router doesn’t support the newer SMB protocol.

I just recently wiped my computer and installed KUbuntu 24.04 LTS and I tried adding that same line of code to the smb.conf file, but when I try to go to the IP address of my router it tells me that “Connection to host 192.168.1.1 is broken”.

I’ve been trying to find a solution online, but not having luck.

Anyone have any suggestions?

  • Galaxy_m105@lemmy.worldOPEnglish
    0·
    6 months ago

    In KUbuntu 22.04 LTS I had to put in my username and password in settings under “Windows Shares” for it to work. I had password protected the folders in the NAS when I was setting it up in my routers settings page.

      • Galaxy_m105@lemmy.worldOPEnglish
        0·
        6 months ago

        It’s a Linksys model EA7300 router. It shows up to date on the firmware being at 1.0.11.200282.

        • bloodfart@lemmy.ml
          0·
          6 months ago

          hardware version?

          e: i looked and there’s only v1 and v2 and they’re both supported by openwrt. you can use the openwrt alternative router firmware to enable many more options and abilities. your router is dual firmware too, so it’s possible to keep the old one installed in case you wanna jump back to it.

          you can (when you feel like it) make your router into a real-ass linux based gateway router that does all kinds of crazy shit like lets you use SMB2 and up to access files shared from it and other things

          install openwrt on v1

          install openwrt on v2

          setup samba filesharing on openwrt

            • bloodfart@lemmy.ml
              0·
              6 months ago

              Take your time and don’t rush, make sure you understand what you’re trying to do and how to do it. Double check that everything still works and verify that you know how to get to the “b” firmware incase you screw up the “a”. Verify that the “b” is configured appropriately.