RE: [Evolution] Can't connect to exchange server after networkinterface changes

["Chris White" <cwhite fortresstech com>]

Yeah, that's pretty much what I figured.  When I go home tonight, I'll
verify what's still left around after a force-shutdown and see what
happens.

Thanks
...cj
 
> Hmm, it sounds like the exchange backend, which is another process, is
> still running, even when force-shutdown is invoked.
>
> Try looking for an evolution-exchange-component process perhaps?
>
>
> On Wed, 2005-05-04 at 08:01 -0400, Christopher J. White wrote:
> > I'm using evolution 2.0.4 on a FC3 laptop.  I'll be at work happily
> > connecting to the exchange server to retrieve email.  I close down
> > evolution (even doing --force-shutdown to close the other
components).
> > Then I take my laptop home.
> >
> > Once home, my ethernet interfaces change.  Usually I'm going from
wired
> > (eth0) to wireless(eth1), with my connection to the server now over
a
> > VPN interface (cipsec0).  I can connect to the internet just fine,
and
> > ping the exchange server and access all servers over the VPN, but
for
> > some reason evolution seems to get confused.  As soon as I open the
> > exchange root folder, it gets stuck at the message "Scanning
exchange
> > folders on server.." in the status bar (or something like that).  It
> > never completes.  Sometimes it will even show two info messages like
> > that.
> >
> > I've tried --force-shutdown and restart, but still no luck.  If I
then
> > bring my laptop back to work and revert the interfaces to work mode,
> > evolution starts up and connects just fine.
> >
> > If I do a complete linux shutdown and reboot, it clears up, but then
> > when I get back to work it no longer connects.
> >
> > Any ideas?
> >
> > ...cj
> >
> > _______________________________________________
> > evolution maillist  -  evolution lists ximian com
> > http://lists.ximian.com/mailman/listinfo/evolution