On 12-09-05 8:51 AM, mayak-cq wrote:
On Tue, 2012-09-04 at 15:28 -0400, Ludovic Marcotte wrote:
On 04/09/12 15:27, mayak-cq wrote:
> Yes it is -- listens on 139 and 445 bot not 135 and no ldap :-(
Do you have an other LDAP server running on the same machine?
If no, you can always start it manually using"samba -d 5 -i -M single"
and post the output.
Bonjour Ludovic,
Well -- that was it -- I was starting samba using the
/etc/rc.d/init.d/samba4 script. I'm still ignorant on the issue, but
obviously starting samba using /usr/sbin/samba is substantively
different that with /usr/sbin/smbd (which is what the init script uses).
Do you know the difference? smbd does not start ldap and port 135, but
is started as a child process using the samba executable.
The init script for samba4 on rhel starts smbd, I fixed it yesterday to
start 'samba' instead.
The new init script will be available with the next samba build,
meanwhile, either start it manually like you did, or replace 'smbd' by
'samba' in the current init script.
Thanks :-)
M
--
Jean Raby
[email protected] :: +1.514.447.4918 (x120) :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
--
[email protected]
https://inverse.ca/sogo/lists
