[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: MessageID integer problem
> Hi Everyone,
>
> I have a question on the Open LDAP client (ldapmodify). I have run into a
> problem. I have written a small server application in .NET that 'talks'
> LDAP. I use the openldap utilities to send data to this server
> application.
> Everything seems to work fine until I reach message ID (in LDAP message
> header) 32.768 (yes, I know, no cooincidence here). Message ID 32.767 gets
> sent as 02 02 7f ff. On my windows machine the OpenLdap software sends me
> 02
> 03 00 80 00 for the next message ID where the 00 80 00 is the actual
> message
> ID number. This is what I would expect. On Windows all seems to work OK.
>
> When I have a client on an Unix machine I get 02 03 00 80 ff. This
> calculates into 33.023. It looks like the wrong bytes get updated. I
> return
> the exact same message ID in my modify result, but this causes the client
> to
> hang. My guess is it is expecting a different number. I have tried sending
> back the correct number in this case (or at least what I believe to be
> correct), 02 03 00 80 00. This however does not solve the problem.
>
> I am somewhat stuck.
>
> Does anyone have any suggestions for me? What am I missing here?
>
> Any help would be very much appreciated.
Your problem sounds quite interesting; unfortunately your report is
absolutely vague, since you don't specify the type and the version of the
various pieces of software you're using: what client (ok, ldapmodify),
what client version, what server (ok, you made it; did you write the BER
encoding/decoding, or did you recycle those from OpenLDAP's liblber? In
case, what version?), what OS (you say Windows and Unix, it's like saying
Fiat and Renault) what OS version.
Can you be more precise?
p.
--
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497