|
Is there a firewall in the mix that's blocking port 389 to the company.com box? How about rules on that box that control what servers are allowed to talk to it directly? Matt -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Cassidy, Alan Sent: Thursday, July 06, 2006 4:01 PM To: RPG programming on the AS400 / iSeries Subject: RE: LDAP connections to the proper server, and unknown error?? Yes, thanks Scott, and I'm going to check on that. I had originally simply wanted to just anonymously validate the user portion of the email address against the LDAP server, which does not require a logon, because it is simply meant to validate the left side of the address. Of course at this time the ldap_search_st() seems to get past an error whereas ldap_search() does not. I think if I can get past the connection issue that I can work out the rest of the details using your example code (thanks again), and the feedback from our local yokel here on the details in the directory. The connection issue at this time is that the LDAP API's, and the ldapsearch command issued within Qshell, do not work with the proper LDAP server name ("company.com"). The LDAP directory is spread over several Windows boxes, but access to the "composite" directory is through the server name "company.com". I've apparently gotten a good connection to just ONE of those Windows boxes at a time, using the network name of the box. Furthermore, to complicate the scene, the AS400 command line (NOT the shell) is getting a sucessful answer to my PING's to the LDAP server names. That is, "MAIL", "MAIL.COMPANY.COM", and "COMPANY.COM". So there is connection. It's just when using the LDAP client functions it doesn't seem to get it. --Alan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.