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?

  • lemmyreader@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    6 months ago

    According to this Samba 4.16 removed the support for the old SMB1 Protocol.

    Looking here : https://packages.ubuntu.com/search?keywords=samba you can see the difference between Jammy and Noble : 4.15 -> 4.19 So it looks like you’re out of luck with fast and easy solutions. Maybe downloading the older Samba package and its dependencies and downgrade and then put the package on “hold” is maybe possible. During such an attempt using aptitude instead of apt could be helpful.

    • Avid Amoeba@lemmy.ca
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      6 months ago

      Or do something funky like using a privileged Docker container built from 22.04 (or anything else with old enough samba) to mount the samba share onto a volume that sits on the host OS. 😂

      Something like:

      • Create a mount point, say /media/myshare
      • docker run --privileged -it --rm -v /media/myshare:/mnt ubuntu:22.04 bash
      • mount -t cifs //<host>/<path> /mnt -o user=<user>,password=<user>
      • Check the contents of /media/myshare on the host.

      If it works, you could bake this into a startup script for the Docker image. Run it with the appropriate --cap-add instead of --privileged. Start it on boot via systemd.

      • Max-P@lemmy.max-p.me
        link
        fedilink
        arrow-up
        3
        ·
        6 months ago

        Docker would still go through the kernel for the mount, that’s one of the few things Docker can’t do because it’s the same kernel as the host.

        That said I doubt it’s been removed from the kernel, only the Samba server. OP is a client.

        • Avid Amoeba@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          6 months ago

          Yeah but some of the samba mounting mechanism is outside of the kernel. The protocol deprecation might just be in a separate package. 🥹 I haven’t checked.

      • Galaxy_m105@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        Lol, I will need to become more familiar with how to use docker. I know how to use virtual box so I may try to run vm with 22.04. I’m still pretty new and starting my Linux Journey. 🙂

    • Galaxy_m105@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 months ago

      Ah…well crap. It is an old router. I checked for firmware updates on it, but I doubt that they’ll bring in support for newer SMB versions. I may have to get a new router at some point. Thanks for the feedback!

  • Galaxy_m105@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    6 months ago

    Thank you all for the feedback! I posted the same on Reddit at the same time and haven’t gotten any replies from Reddit yet. Looks like the power users came to Lemmy after the whole Reddit fiasco. 🙂 I’m liking it pretty well here so far. 🙂

    • Galaxy_m105@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      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.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          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
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            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
                link
                fedilink
                arrow-up
                2
                ·
                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.

    • Galaxy_m105@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      I’m going to check my router again for firmware/software update, but I don’t that it has support for newer SMB protocol.