Built and tested r1340 today and confirmed that openchangeclient still
segfaults when checking the freebusy status of a resource.  Here is a
verbose dump of the transaction:

Using binding ncacn_ip_tcp:192.168.36.205
Mapped to DCERPC endpoint 135
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Mapped to DCERPC endpoint 5000
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Cannot do GSSAPI to an IP address
Failed to start GENSEC client mech gssapi_krb5:
NT_STATUS_INVALID_PARAMETER
Got challenge flags:
Got NTLMSSP neg_flags=0x62898205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_CHAL_TARGET_INFO
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60088205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
Using binding ncacn_ip_tcp:192.168.36.205
Mapped to DCERPC endpoint 135
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Mapped to DCERPC endpoint 5002
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Cannot do GSSAPI to an IP address
Failed to start GENSEC client mech gssapi_krb5:
NT_STATUS_INVALID_PARAMETER
Got challenge flags:
Got NTLMSSP neg_flags=0x62898205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_CHAL_TARGET_INFO
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60088205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
Using binding ncacn_ip_tcp:192.168.36.205
Mapped to DCERPC endpoint 135
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Mapped to DCERPC endpoint 5001
added interface ip=192.168.224.60 nmask=255.255.254.0
added interface ip=192.168.224.60 nmask=255.255.254.0
Cannot do GSSAPI to an IP address
Failed to start GENSEC client mech gssapi_krb5:
NT_STATUS_INVALID_PARAMETER
Got challenge flags:
Got NTLMSSP neg_flags=0x62898205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_CHAL_TARGET_INFO
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60088205
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
ndr_pull_error(2): Bad switch value 0

Ian
  
On Sun, 2009-04-19 at 15:38 +0200, Julien Kerihuel wrote:
> On Sat, 2009-04-18 at 09:54 -0400, Ian Anderson wrote:
> > If I configure the mapiprofile with an IP address for a server that does
> > not have the Public Folders store on it, the openchangeclient fails with
> > a not found error.  
> 
> Hi Ian,
> 
> I should have rather expected a ecWrongServer error here. Can you try
> trunk r1324 and tells me if it makes any difference?
> 
> > If I configuring it with the correct IP address it
> > succeeds (most of the time).  This does not seem to affect fetchmail
> > operations (I can get inbox items regardless of which IP address the
> > profile is configured with).  Can anyone else confirm this behavior?
> 
> I'm not sure I fully understand what you mean by "most of the time" ;-)
> I would need additional details so I may properly help you.
> 
> > When I do have the Public Folders server configured in the profile, I am
> > able to retrieve freebusy information for users, but when I try to
> > retrieve freebusy information for a resource the openchangeclient
> > segfaults.  Can anyone else confirm this behavior?
> 
> Can you create a trac ticket on http://trac.openchange.org with steps to
> perform to reproduce this problem?
> 
> Cheers,
> Julien.
> 
> _______________________________________________
> devel mailing list
> [email protected]
> http://mailman.openchange.org/listinfo/devel

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to