[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Thu, 30 Apr 2009 16:39:04 +0100 Simon Waters wrote: > Grant Sewell wrote: > > On Thu, 30 Apr 2009 14:23:22 +0100 > > Simon Waters wrote: > > > >> Grant Sewell wrote: > >>> Any suggestions? > >> Does "ldapsearch" do anything meaningful? > >> > >> ldapsearch -x -b "dc=domain,dc=tld" -D > >> "cn=Administrator,dc=domain.tld" -p 389 -h dns.name.ad.server > > > > $ ldapsearch -x -b "dc=domain,dc=tld" -D > > "cn=Administrator,dc=domain,dc=tld" -p 389 -h server.domain.tld > > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) > > > > $ ldapsearch -x -b "dc=domain.ld" -D > > "cn=Administrator,dc=domain.tld" -p 389 -h server.domain.tld > > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) > > > > Hmm. :( > > Offtopic perhaps but "netstat -an" on Windows shows port 389 > listening? > > nmap shows it now firewalled away? Not off-topic. :D Interestingly Windows is "listening" on 0.0.0.0:389, but not on 192.168.1.252:389 (not that it should matter - 0.0.0.0:389 is contactable anyway since it's the "everything" address). Likewise, nmap shows 389 as being open. Grant. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html