-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Tuesday, September 06, 2005 6:55 AM To: CentOS ML Subject: RE: [CentOS] LDAP/iptables
On Tue, 2005-09-06 at 06:31 -0400, Thomas E Dukes wrote:
<snip> > Ooops, I found the typo, too. Fixed it but still won't connect. > > > > > Have you tried rebooting? (I know, I know :) Sometimes system > > updates can cause subtle issues from time to time. Maybe something > > is goofy with the network on your machine. Have you been starting > > and stopping the network service? Can you ping localhost? I have > > seen some linux boxes (been a while, > > though) forget about how to talk to localhost and it caused all > > sorts of weird behavior. > > Yes, I have rebooted but to no avail. Also, I can ping 'localhost', > 'palmettodomains.com', '127.0.0.1' and '10.10.0.1'. I still can't > figure why I can't telnet to one of those using port 389. >
You can't connect to port 389 because you are not listening on port 389 :)
Until a netstat (or lsof) shows you are listening on port 389, you will not be able to connect to it.
As a shot in the dark, are you running with selinux enabled? It has caused many a subtle problem in which a configuration that should "just work" has failed to work. Try running
setenforce 0 and
then restarting ldap. I run my machines with selinux=0 on
the kernel
line in grub.conf
No, I don't run selinux.
Make doubly sure ... look at the file /etc/sysconfig/selinux and set the line:
SELINUX=Disabled
Hi Johnny,
Mine is located at /etc/selinux/config. It is set to disabled. Also, I have selinux=0 in my grub.conf.
I really appreciate everyones help on this.
Thanks!!
then reboot