Entourage 2004 "Not Connected" Intermittent Message with Kerio MailServer

All,

We support an office of about 15 mail users running Kerio for the
backend and Entourage 2004 for an email client. Kerio was recently
updated to version 6.4.0 and all Entourage users are on version 11.3.3
and are fully patched.

Starting last week, shortly following the 6.4.0 update users
intermittently get a "Not Connected" message in Entourage right next
to their mail account inbox. Sometimes this happens after they have
been in Entourage for awhile. Other times it happens right when they
launch it. It seems to move from user to user. At any given moment
there are probably 1-3 users who cannot connect.

They can connect fine with webmail. The problem started shortly after
the 6.4.0 update, so I assume it may be related and I have a ticket
open with Kerio, but no results thus far.

Wondering if anyone has any thoughts about what might cause this? It
seems to have affected most if not all Entourage users and nothing has
changed with their local settings. With one user I did completely
delete their local account and mail database, rebuilt it and same
result.

Thanks

timothy
Fri Jun 15 07:49:26 CDT 2007

No ideas on this one? Going to be following up with Kerio again today,
but was curious if anyone else had thoughts?

On Jun 13, 8:58 am, timothy.hat...@gmail.com wrote:
> All,
>
> We support an office of about 15 mail users running Kerio for the
> backend and Entourage 2004 for an email client. Kerio was recently
> updated to version 6.4.0 and all Entourage users are on version 11.3.3
> and are fully patched.
>
> Starting last week, shortly following the 6.4.0 update users
> intermittently get a "Not Connected" message in Entourage right next
> to their mail account inbox. Sometimes this happens after they have
> been in Entourage for awhile. Other times it happens right when they
> launch it. It seems to move from user to user. At any given moment
> there are probably 1-3 users who cannot connect.
>
> They can connect fine with webmail. The problem started shortly after
> the 6.4.0 update, so I assume it may be related and I have a ticket
> open with Kerio, but no results thus far.
>
> Wondering if anyone has any thoughts about what might cause this? It
> seems to have affected most if not all Entourage users and nothing has
> changed with their local settings. With one user I did completely
> delete their local account and mail database, rebuilt it and same
> result.
>
> Thanks

Jeff
Fri Jun 15 11:56:19 CDT 2007

On 6/15/07 5:49 AM, in article
1181911766.625156.173640@w5g2000hsg.googlegroups.com,
"timothy.hatter@gmail.com" <timothy.hatter@gmail.com> wrote:

> No ideas on this one? Going to be following up with Kerio again today,
> but was curious if anyone else had thoughts?

I've been using Kerio MailServer at a client site with no issues, but
haven't upgraded to 6.4. I've found "Not Connected" errors to be network
problems whenever they have cropped up for me. Obviously, if a user can
connect via webmail while Entourage cannot connect from the same computer,
it's not a network problem.

The only other thing that occurs to me is to check to see if somehow the
maximum number of concurrent connections got reset by the upgrade (for
Entourage clients, this would be in the HTTP/Secure HTTP service setup).

You're probably on the right track pursuing this with Kerio.

Jeff

timothy
Fri Jun 15 15:56:26 CDT 2007

Max number of concurrent HTTP connections is set to 1000. From what I
can see from the logs it doesn't appear it's come close to hitting
this. Perhaps between 100-200 in a 5 minute span and these are spikes.


On Jun 15, 11:56 am, Jeff Zienowicz <j...@jeffz.netINVALID> wrote:
> On 6/15/07 5:49 AM, in article
> 1181911766.625156.173...@w5g2000hsg.googlegroups.com,
>
> "timothy.hat...@gmail.com" <timothy.hat...@gmail.com> wrote:
> > No ideas on this one? Going to be following up with Kerio again today,
> > but was curious if anyone else had thoughts?
>
> I've been using Kerio MailServer at a client site with no issues, but
> haven't upgraded to 6.4. I've found "Not Connected" errors to be network
> problems whenever they have cropped up for me. Obviously, if a user can
> connect via webmail while Entourage cannot connect from the same computer,
> it's not a network problem.
>
> The only other thing that occurs to me is to check to see if somehow the
> maximum number of concurrent connections got reset by the upgrade (for
> Entourage clients, this would be in the HTTP/Secure HTTP service setup).
>
> You're probably on the right track pursuing this with Kerio.
>
> Jeff

MarcNPSmith
Sun Jun 17 05:37:06 CDT 2007

Not connected simply means that Entourage cannot see KMS on the
network!

I use the same setup extensively over https and it's been working
great for the past year in and out of the office...