Prev: V$DIAG_ALERT_EXT table
Next: DBMS_REPAIR.CHECK_OBJECT
From: kat on 21 Apr 2010 14:39 Hi, I'm trying to check the status of our OID (10.1.0.4) server running OEL 4 from another OEL server by passing a string (cn=mytestdb) and I'm hoping to receive an expected string back but I'm getting connection closed by foreign host. Is there a configuration change that has to be made to open up the access? $> telnet oidserver 389 Trying 192.168.2.34... Connected to oidserver. Escape character is '^]'. ldapsearch "cn=mytestdb" Connection to oidserver closed by foreign host. $> I'm able to successfully run ldapsearch "cn=mytestdb" directly on the oidserver. Can someone help? thanks.
From: John Hurley on 21 Apr 2010 15:51 Kat: > Hi, > I'm trying to check the status of our OID (10.1.0.4) server running > OEL 4 from another OEL server by passing a string (cn=mytestdb) and > I'm hoping to receive an expected string back but I'm getting > connection closed by foreign host. Is there a configuration change > that has to be made to open up the access? > > $> telnet oidserver 389 > Trying 192.168.2.34... > Connected to oidserver. > Escape character is '^]'. > ldapsearch "cn=mytestdb" > Connection to oidserver closed by foreign host. > $> > > I'm able to successfully run ldapsearch "cn=mytestdb" directly on the > oidserver. > > Can someone help? > > thanks. Why don't you prove that you can telnet in and run it via a shell script first before trying to figure out why it won't work command line?
From: Shakespeare on 26 Apr 2010 03:47 Op 21-4-2010 20:39, kat schreef: > Hi, > I'm trying to check the status of our OID (10.1.0.4) server running > OEL 4 from another OEL server by passing a string (cn=mytestdb) and > I'm hoping to receive an expected string back but I'm getting > connection closed by foreign host. Is there a configuration change > that has to be made to open up the access? > > $> telnet oidserver 389 > Trying 192.168.2.34... > Connected to oidserver. > Escape character is '^]'. > ldapsearch "cn=mytestdb" > Connection to oidserver closed by foreign host. > $> > > I'm able to successfully run ldapsearch "cn=mytestdb" directly on the > oidserver. > > Can someone help? > > thanks. Your OID server is not running telnet on port 389, that is the port for LDAP. Telnet should normally be running on the normal telnet port. But you don't need telnet at all to perform an ldap search on another server. You can use ldapsearch on the second server with the target host and target port as parameters, like: ldapsearch -h <targethost> -p <targetport> -D cn=orcladmin -w <password> -b <basedn> (cn=mytestdb) Shakespeare
From: Carlos on 26 Apr 2010 05:22 On Apr 26, 9:47 am, Shakespeare <what...(a)xs4all.nl> wrote: > Op 21-4-2010 20:39, kat schreef: > > > > > Hi, > > I'm trying to check the status of our OID (10.1.0.4) server running > > OEL 4 from another OEL server by passing a string (cn=mytestdb) and > > I'm hoping to receive an expected string back but I'm getting > > connection closed by foreign host. Is there a configuration change > > that has to be made to open up the access? > > > $> telnet oidserver 389 > > Trying 192.168.2.34... > > Connected to oidserver. > > Escape character is '^]'. > > ldapsearch "cn=mytestdb" > > Connection to oidserver closed by foreign host. > > $> > > > I'm able to successfully run ldapsearch "cn=mytestdb" directly on the > > oidserver. > > > Can someone help? > > > thanks. > > Your OID server is not running telnet on port 389, that is the port for > LDAP. Telnet should normally be running on the normal telnet port. > > But you don't need telnet at all to perform an ldap search on another > server. You can use ldapsearch on the second server with the target host > and target port as parameters, like: > ldapsearch -h <targethost> -p <targetport> -D cn=orcladmin -w <password> > -b <basedn> (cn=mytestdb) > > Shakespeare I respectfully disagree with the term 'normal telnet port' (which I presume Shakespeare assumes 23 ). Telnet establishes connection between any different ports (as per RFC 854), and only if intended as remote terminal access this protocol is assigned server port 23. Cheers. Carlos.
From: Shakespeare on 26 Apr 2010 06:44
Op 26-4-2010 11:22, Carlos schreef: > On Apr 26, 9:47 am, Shakespeare<what...(a)xs4all.nl> wrote: >> Op 21-4-2010 20:39, kat schreef: >> >> >> >>> Hi, >>> I'm trying to check the status of our OID (10.1.0.4) server running >>> OEL 4 from another OEL server by passing a string (cn=mytestdb) and >>> I'm hoping to receive an expected string back but I'm getting >>> connection closed by foreign host. Is there a configuration change >>> that has to be made to open up the access? >> >>> $> telnet oidserver 389 >>> Trying 192.168.2.34... >>> Connected to oidserver. >>> Escape character is '^]'. >>> ldapsearch "cn=mytestdb" >>> Connection to oidserver closed by foreign host. >>> $> >> >>> I'm able to successfully run ldapsearch "cn=mytestdb" directly on the >>> oidserver. >> >>> Can someone help? >> >>> thanks. >> >> Your OID server is not running telnet on port 389, that is the port for >> LDAP. Telnet should normally be running on the normal telnet port. >> >> But you don't need telnet at all to perform an ldap search on another >> server. You can use ldapsearch on the second server with the target host >> and target port as parameters, like: >> ldapsearch -h<targethost> -p<targetport> -D cn=orcladmin -w<password> >> -b<basedn> (cn=mytestdb) >> >> Shakespeare > > I respectfully disagree with the term 'normal telnet port' (which I > presume Shakespeare assumes 23 ). > > Telnet establishes connection between any different ports (as per RFC > 854), and only if intended as remote terminal access this protocol is > assigned server port 23. > > Cheers. > > Carlos. I stand corrected, Carlos is right here, as the server responds with "connected to oidserver". Still, telnet is not needed here, so you could try to perform ldapsearch directly. Shakespeare |