http://wiki.alfresco.com/wiki/Changing_Bind_Addresses_and_Ports_for_Samba_and_FTP
Word from the wise. Avoid doing redirects like above. They are recipes for cat fights between Samba and Alfresco. Loopback is in fact 127.*. .*
under Linux. So 127.0.0.2
could have been giving to Alfresco so leaving 127.0.0.1
to samba. In host file you can declare a name owning to .localdomain
or what ever the network wide DNS lookup will be.
To be truthful without setting Alfresco and samba to own zones it is a straight up recipe for cat fights between them at some point.
There is a major bug alfresco documentation when it comes to setting samba. http://lists.samba.org/archive/samba/1997-November/004810.html Don't use socket address at all. Only use interfaces stuff in samba config
interfaces = 192.168.129.2/255.255.255.0 127.0.0.1
bind interfaces only = yes
Notice the 192.168.129.0
in the Alfresco example is now a 192.168.129.2
. Yes this is the correct way to declare samba address. Also notice they missed the 127.0.0.1
fact that is required so samba tools work.
Basically its better to tell the two programs to go stand in there own areas straight off bat.
Why must samba have 127.0.0.1
even if you are not running samba. smbpasswd
and other samba tools will attempt to access 127.0.0.1
. Yes cat fights. Some of sambas tools expect samba to be 127.0.0.1
they break if it not. Yes samba tools accessing alfresco might break alfresco as well. Its just highly not a good idea to redirect 127.0.0.1 particularly when we have tones more loopback addresses.
Yes both alfresco and samba are both going after exactly the same interfaces. Alfresco is the alien. Alfresco will not have PAM the Linux login system using it. So 127.0.0.1
should be kept out of Alfresco hands.