I've just spent the day digging into nas4free's samba implementation, and it's fair to say that I'm "less than impressed".
The highlights of what is broken:
1: When AD is enabled, creation of the Kerberos configuration file seems to be hardcoded into the smbd executable.
2: When adding nas4free to active directory, it caches the administrator password in plaintext in config.xml.
3: The default variables in the smb.conf file are just plain broken, and the gui is too stupid to help deal with this.
4: The samba rc script tries to rejoin the domain every time the service is started, but the service never renews tickets.
Seriously: what the f_*? If this isn't going to be fixed in the next release, just do everyone a favor and take CIFS support out of the product.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
For the Love of God - Will Someone Please Fix Samba?
-
WarrenV
- NewUser

- Posts: 11
- Joined: 17 May 2014 04:36
- Status: Offline
- apollo567
- Site Admin

- Posts: 675
- Joined: 23 Jun 2012 06:37
- Location: Ludwigshafen, Germany
- Status: Offline
Re: For the Love of God - Will Someone Please Fix Samba?
Well please reflect in your discussion N4F is a project of volunteers, so If you have coding / System design capabilities you are more than invited to participate. Aside of this as the software is quite a gain for the user 'as it is'. So keep this in mind but everyone knows there is always room to improve....WarrenV wrote:I've just spent the day digging into nas4free's samba implementation, and it's fair to say that I'm "less than impressed".
The highlights of what is broken:
1: When AD is enabled, creation of the Kerberos configuration file seems to be hardcoded into the smbd executable.
2: When adding nas4free to active directory, it caches the administrator password in plaintext in config.xml.
3: The default variables in the smb.conf file are just plain broken, and the gui is too stupid to help deal with this.
4: The samba rc script tries to rejoin the domain every time the service is started, but the service never renews tickets.
Seriously: what the f_*? If this isn't going to be fixed in the next release, just do everyone a favor and take CIFS support out of the product.
my NAS and its development until today: viewtopic.php?f=63&t=39&sid=039fed830cf ... 4d0abe4a04