I tried the command you posted and I had the same problem, with and without the -E flag. I'll try to figure out where is outlook connecting.
If anyone was able to connect to exchange.ms successfully, I'll appreciate your experience :) Thanks a lot On 13 October 2010 10:18, Pablo Saavedra <pablo.a.saave...@gmail.com> wrote: > Thanks, it looks like the reply-to is not properly configured :). I'll try > that and let you know how it went > > > > On 13 October 2010 10:09, Milan Crha <mc...@redhat.com> wrote: > >> On Wed, 2010-10-13 at 09:49 -0300, Pablo Saavedra wrote: >> > Thanks, it looks like the reason is a network timeout: >> > >> > Failed to connect host 64.71.238.24 on port 135 - NT_STATUS_IO_TIMEOUT >> > Failed to connect host 64.71.238.24 (mse18fe2.mse18.exchange.ms) on >> port 135 >> > - NT_STATUS_IO_TIMEOUT. >> > >> > I tried to telnet but the port is closed. However, one of my workmates >> has >> > windows and was able to setup outlook automatically without any problem. >> > >> > Any ideas which port it might be using? This is exchange 2007, at least. >> >> Hi, >> I'm sorry, I have no idea. Try to create a profile like this: >> mapiprofile -c -P test -I mse18fe2.mse18.exchange.ms -D windows_domain >> -u user -p password >> and when it will resist with other than IO_TIMEOUT error, then maybe >> also add -E for encrypted connection. >> >> I would try to 'tracert' to that machine from your colleagues windows >> machine, maybe it resolves to a different destination machine. >> Bye, >> Milan >> >> P.S.: you, probably incidentally, replied only to me >> >> >
_______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
