8:38 p.m.
Hi Guys,
I have some strange issue where FreeIPA 4.6.1 accepts telnet connections on port 636 but
no bind. Both are successful on 389.
This didn't happen on 4.5.4.
Any idea ?
Thanks,
Matt
2:03 p.m.
New subject: FreeIPA 4.6.1 cannot bind on 636 but can connect on port.
No-one a clue about this ?
2:32 p.m.
New subject: FreeIPA 4.6.1 cannot bind on 636 but can connect on port.
hi,
could you try using ldapsearch with the -d 10 switch? That shoud give you
plenty of debugging info.
--
Groeten,
natxo
9:19 a.m.
New subject: FreeIPA 4.6.1 cannot bind on 636 but can connect on port.
Hi,
I can do!
Can it be that the certificate, self signed, is more of a security issue now and that
causes the problem ? In the past I was able to use a selfsigned one for internal tests.
Cheers,
Matt
9:51 a.m.
New subject: FreeIPA 4.6.1 cannot bind on 636 but can connect on port.
Matt . via FreeIPA-users wrote:
Hi,
I can do!
Can it be that the certificate, self signed, is more of a security issue now and that
causes the problem ? In the past I was able to use a selfsigned one for internal tests.
As I asked in IRC you need to provide a GOOD description of what you are
doing, what output you are seeing and what you expect to see. Including
full command-line, stdout, etc. And I guess particularly where these
certs came from, how you generated them, etc.
rob
2277
days inactive
2285
days old
freeipa-users@lists.fedorahosted.org
4 comments
3 participants
participants (3)
-
Matt . -
Natxo Asenjo -
Rob Crittenden