WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Samba 3 outdated SMB protocoll TC15  (Read 207 times)

Offline echozephyr

  • Newbie
  • *
  • Posts: 3
Samba 3 outdated SMB protocoll TC15
« on: September 17, 2024, 08:07:38 AM »
Hi everyone, i revently got TC on a Thin client installed to use a a small network drive for cold storage. It works well, i managed to setup SSH and VNC without issue, but i seem to have hit a snag with samba, the versions available to me in the app browser is samba3. I have set it up no problem, but my windows11 machines wont connect to it due to the smb1 protocoll. I have tried changing the config file to include things like         client min protocol = SMB3
client max protocol = SMB3
protocol= SMB3
without luck. Has anyone encountered this issue too?

Online gadget42

  • Hero Member
  • *****
  • Posts: 712
Re: Samba 3 outdated SMB protocoll TC15
« Reply #1 on: September 17, 2024, 09:08:33 AM »
« Last Edit: September 17, 2024, 09:19:26 AM by gadget42 »
The fluctuation theorem has long been known for a sudden switch of the Hamiltonian of a classical system Z54 . For a quantum system with a Hamiltonian changing from... https://forum.tinycorelinux.net/index.php/topic,25972.msg166580.html#msg166580

Offline echozephyr

  • Newbie
  • *
  • Posts: 3
Re: Samba 3 outdated SMB protocoll TC15
« Reply #2 on: September 17, 2024, 01:02:26 PM »
Thanks for taking a second :)
I am able to connect to Samba in so far as Windows tells me that it wont allow the connection as the samba share uses SMB1-Protocoll, which is no longer supported since 2017. I could probably install it with some minor effort, but i would like to keep the option open to open up my cold storage to the internet at some point, which would then pose a security risk with SMB1.
 :)

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1212
Re: Samba 3 outdated SMB protocoll TC15
« Reply #3 on: September 17, 2024, 01:16:17 PM »
Im going to guess that samba3 is too old to work with windows 11 (even though you are wanting to use SMB3).

Can you run x86_64?  Samba in that repo is samba4.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11500
Re: Samba 3 outdated SMB protocoll TC15
« Reply #4 on: September 17, 2024, 02:23:11 PM »
Hi echozephyr
Try adding this to the  [global]  section of your  smb.conf  file:
Code: [Select]
min protocol = SMB2

Offline echozephyr

  • Newbie
  • *
  • Posts: 3
Re: Samba 3 outdated SMB protocoll TC15
« Reply #5 on: September 19, 2024, 02:39:20 AM »

Can you run x86_64?  Samba in that repo is samba4.

The machine is x86_64, it has a AMD GX-212ZC, do i have to change somethin on my TC to change the repo? I am not very familiar with TC yet :D

Try adding this to the  [global]  section of your  smb.conf  file:
Code: [Select]
min protocol = SMB2

That sadl did not work :(

Online gadget42

  • Hero Member
  • *****
  • Posts: 712
Re: Samba 3 outdated SMB protocoll TC15
« Reply #6 on: September 19, 2024, 04:53:30 AM »
from here:
http://tinycorelinux.net/downloads.html
to here:
http://tinycorelinux.net/ports.html
to here:
http://tinycorelinux.net/15.x/x86_64/release/
and pick:
CorePure64 for no GUI
or:
TinyCorePure64 for GUI
The fluctuation theorem has long been known for a sudden switch of the Hamiltonian of a classical system Z54 . For a quantum system with a Hamiltonian changing from... https://forum.tinycorelinux.net/index.php/topic,25972.msg166580.html#msg166580

Offline Leee

  • Full Member
  • ***
  • Posts: 111
Re: Samba 3 outdated SMB protocoll TC15
« Reply #7 on: September 19, 2024, 05:38:03 AM »
On TC 15.0 / x86_64, samba.tcz seems to depend on libtirpc.tcz but it's not mentioned in the .dep file.

core 15.0 x86_64

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11500
Re: Samba 3 outdated SMB protocoll TC15
« Reply #8 on: September 19, 2024, 10:53:40 AM »
Hi echozephyr
... That sadl did not work :(
You did remove any  SMB3  references, right?

If your [global] section contains:
Code: [Select]
security = sharetry changing it to:
Code: [Select]
security = usr
You might also want to examine the log file for messages and errors.
Check  log file =  in  [global]  for the location.