@all
first of all please excuse my long absence. I have seen your requests for translation, but I am currently changing my job, and in fact I am working on two contracts in parallel... So here is my translation
First of all I have to admit that I don't have an entire clean solution: it is sort of botched together. So use this approach with care. Today I have seen an update in this other German thread, and I hope that I will be able to drive it a little further.
So what does the approach provide? The second slave SME "integrates" into the domain in that way that it provides WINS services for the local network segment. However there are still two separate user databases which need to be updated in parallel (first SME being the domain controller with option "DomainController: Yes" and the second SME with option "DomainController: No"). This is not too much a problem for me because I have a VERY limited number of users in the second network segment.
This is the concept:
- Configure first SME through web-GUI to become domain controller
- Configure second SME through web-GUI to be NOT a domain controller
- Create customized templates on second SME with necessary Samba options
The use of custom templates will keep applied tweaks even though the SME distro might be updated or changes of the Samba configuration are applied through the web-GUI.
All following steps should be performed in a root shell.
Create /etc/e-smith/templates-custom/etc/smb.conf/11winsLocalMaster :
return "local master = yes";
Create /etc/e-smith/templates-custom/etc/smb.conf/11winsOsLevel :
return "os level = 65";
Create /etc/e-smith/templates-custom/etc/smb.conf/11winsPreferredMaster :
return "preferred master = yes";
Create /etc/e-smith/templates-custom/etc/smb.conf/11winsProxy :
return "wins proxy = yes";
Create /etc/e-smith/templates-custom/etc/smb.conf/11winsServer :
return "wins server = <IP-address or DNS of first SME-Server>";
Then expand template(s) i.e. run (the following command is currently based on best guess, sorry!)
expand-template /etc/samba/smb.conf
Now restart Samba demon:
/etc/init.d/smbd restart
Alternatively reboot SME server.
That's it. Be aware of the fact that I achieved NetBIOS name resolution just in the slave network: the NetBIOS names of those machines are replicated up to the SME domain controller, but not vice versa. I did not figure out why this is the case.
So folks: good success now. Please post further thoughts, results, suggestion.
Thanks to all in this forum, turandot.