Re: Bind failure

[Mark W. <mew...@un...>]

There are bugs in 5.6 that Net::LDAP exposes. This might be one of
them. Either downgrade to a pre 5.6 release like 5.0005 of Perl or wait
until 5.6.1.

Mark

On Fri, 23 Jun 2000, Klunder, JAA (Hans) wrote:

> Hi,
> 
> I'm trying to run perl-ldap on NT 4.0. running perl 5.6  (activestate)
> I installed perl-ldap-0.19 and Convert-ASN1.0.07 
> 
> The server is LDAP V3 compliant (according to the supplier)  and works with
> several clients.
> 
> I use the following script to get to my server:
> 
> #-----
> use Net::LDAP qw(:all);
> use Net::LDAP::Util qw( ldap_error_name
>                           ldap_error_text) ;
>                       
> my $ldap = Net::LDAP->new("10.1.1.144",debug => 3) or die "$@";
> my $mesg = $ldap->bind(version => 3
> 			) or die "$@";        
> #------
> 
> This results in:
> 
> Net::LDAP=HASH(0x8e9f190) sending:
> 
> 30 0C 02 01 01 40 07 02 01 03 04 00 80 00 __ __ 0....@........
> 
> Net::LDAP=HASH(0x8e9f190) received:
> 
> 30 38 02 01 00 78 33 0A 01 02 04 00 04 14 55 6E 08...x3.......Un
> 6B 6E 6F 77 6E 20 72 65 71 75 65 73 74 20 74 79 known request ty
> 70 65 8A 16 31 2E 33 2E 36 2E 31 2E 34 2E 31 2E pe..1.3.6.1.4.1.
> 31 34 36 36 2E 32 30 30 33 36 __ __ __ __ __ __ 1466.20036
> 
> And the request type is indeed unknown. When I look at the traffic using NT
> network monitor it defines the operation as BindRequest (hex 40).
> However if I bind using another Ldap client (ldp)  the network monitor shows
> the BindRequest as hex 60.
> 
> I found out that I can change asn_application in ASN1.pm from 40 to 60 and
> then the bind succeeds, however, the search then dies because the results
> can't be parsed by perl LDAP.
> 
> Any hints ?
> 
> Hans
> 
>  
> 
> ================================================
> De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
> is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
> onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
> de afzender direct te informeren door het bericht te retourneren. 
> ================================================
> The information contained in this message may be confidential 
> and is intended to be exclusively for the addressee. Should you 
> receive this message unintentionally, please do not use the contents 
> herein and notify the sender immediately by return e-mail.
> 
> 
> 
>