On Mon, Jan 4, 2010 at 6:25 PM, Julien Kerihuel <[email protected]> wrote: >> >> If it has not been tested then surely something is wrong somewhere. > > ^^^ It has been tested ;-)
Sorry Julien. I just realized that it might have to do with some local auth issue. I am reinstalling Exchange on my own private test environment. I shall let you know how things go. Looks like I jumped the gun. Sorry. > I've rerun complete samba4 + openchange install + provision and test on > 3 different workstations with different operating systems (Ubuntu 9.10, > Fedora 12 and FreeBSD 8.0). > > I've also made tests with either samba4-alpha9 or 10. > As I said, it seems to be an Exchange issue. I shall get back soon. I hope to get things going very soon. Wait for an update. > Finally I've tested openchangeproxy vs Exchange 2003 and 2010. > Okay. >> There are talloc incompatibility issues and it is quite a headache. >> >> I just now banged into a samba compile failure. > > You definitely have a conflict with existing/previous install. Please, > make sure you've wised up any previous samba4 install before proceeding > (maybe incorrect PKG_CONFIG_PATH env var value?) > > Running 'make samba4' from openchange trunk directory does automatize > the full samba4 install process properly. Well that doesn't work since I never set the PKG_CONFIG variable. Anyway never mind all that. I hate to use old stuff. Let me get back to you after the Exchange reinstall. >> Can you please see what is up and fix stuff? > > I can't fix a problem I can't reproduce ... > > I'd need your latest smb.conf output + a outlook-mapiproxy-exchange > wireshark capture. > I shall get you that in case I fail. ;) I run Wireshark on my Outlook box. -Girish _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
