Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!talisker.lacave.net!lacave.net!not-for-mail From: kang cao Newsgroups: comp.lang.ruby Subject: Re: problems using ruby-ldap to connect with windows AD Date: Thu, 14 Apr 2011 09:53:45 -0500 Organization: Service de news de lacave.net Lines: 8 Message-ID: References: <06c30e3c211faaf23530b00c52e1892a@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1302792846 46109 65.111.164.187 (14 Apr 2011 14:54:06 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 14 Apr 2011 14:54:06 +0000 (UTC) In-Reply-To: <06c30e3c211faaf23530b00c52e1892a@ruby-forum.com> X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 381533 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:2849 I have figured out the problem. MY windows AD is listening on 389, not on 636. ldapsearch command works only when I don't put -p in the command line. sorry to bother you all -- Posted via http://www.ruby-forum.com/.