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 manu
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 s
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.
--
Ludovic Marcotte
+1.514.755.3630 :
On Tue, 2012-09-04 at 15:11 -0400, Ludovic Marcotte wrote:
> On 04/09/12 07:34, mayak-cq wrote:
> > i followed the doc, but the provided samba4 package doesn't listen on
> > port 135 when started and it does not appear that that samba ldap
> > instance is running or listening either.
> Is samba4
On 04/09/12 07:34, mayak-cq wrote:
i followed the doc, but the provided samba4 package doesn't listen on
port 135 when started and it does not appear that that samba ldap
instance is running or listening either.
Is samba4 started?
--
Ludovic Marcotte
+1.514.755.3630 :: www.inverse.ca
Inverse
hi all,
i've been having a rough go of getting samba4 and openchange to work on
a centos6x64 installation ...
i followed the doc, but the provided samba4 package doesn't listen on
port 135 when started and it does not appear that that samba ldap
instance is running or listening either.
anyone ha