Re: Blocked UDP Traffic and New Message Notifications
- From: "Chris J" <ChrisJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 08:41:06 -0800
"Lanwench [MVP - Exchange]" wrote:
>
>
> In news:0F451231-CEAC-4241-8CA3-58A18BC2556C@xxxxxxxxxxxxx,
> Chris J <ChrisJ@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:6F6B3C68-5655-44AF-AEF3-B39EC4C5C1EE@xxxxxxxxxxxxx,
> >> Chris J <Chris J@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> >>> Hello all...
> >>>
> >>> I recently discovered that our internal emails weren't being sent
> >>> and received quite as instantaneously as they used to be. Some
> >>> users were also complaining that they weren't receiving any new
> >>> email at all. We are using Exchange 2000 Server, with clients using
> >>> Outlook 2002 (SP3) on Win XP (SP2).
> >>>
> >>> After reading around on the subject I discovered that this is due to
> >>> windows firewall blocking new message notifications from our
> >>> exchange server, as they are sent as UDP packets on random ports.
> >>> There is no way to open up this traffic without seriously
> >>> compromising your firewall.
> >>>
> >>> I have applied the workaround suggested in KB article 839226, but
> >>> unfortunately this has only been partially successful. The
> >>> workaround forces outlook to ask the server if it has any new
> >>> messages via rpc polling. The problem with this is there is no way
> >>> to control the frequency of this polling, and therefore there can
> >>> still be a delay of sometimes a couple of minutes before new
> >>> messages are received. I've got around it at the moment by asking
> >>> the users to go into outlook and change the folder they are
> >>> viewing, which always promts outlook to check for new messages, if
> >>> they want to be absolutly certain they have no new email, though it
> >>> is a bit frustrating.
> >>>
> >>> As an experiment, I tried installing Outlook 2003 on my workstation.
> >>> With no updates applied, Outlook 2003 suffers the same problem as
> >>> 2002. After updating to SP2 and applying the same workaround
> >>> (interestingly, achieved without using rpc polling) email is again
> >>> instantaneous. I would be very interested to know how Outlook 2003
> >>> solves this problem, and if there's any way to achieve the same
> >>> results with Outlook 2002?
> >>>
> >>> Chris Johnson
> >>
> >> Browse to/add outlook.exe as an exception in the Windows firewall on
> >> all clients and see if the problem goes away.
> >>
> >>
> >>
> > Unfortunately I did try that and it didn't work. Well... it works for
> > Outlook 2003, but not for Outlook 2002. Is there anything else that
> > can be done?
>
> Hmmm - I wouldn't think it would be different. Did you browse to the correct
> path to outlook.exe on the OL2002 computers when creating the exception?
> Have you tested disabling the Windows firewall outright to make sure it's
> actually the culprit?
>
>
>
Hello...
Since you were confident the fix should work fine, I did some testing to
check my facts.
It seems (gulp!) that my registry editing is a bit sloppy. I missed out the
"10.0" key, in the registry hack described in KB article 839226. Having
corrected that, the fix seems to work perfectly.
Thanks for the advice!
.
- References:
- Re: Blocked UDP Traffic and New Message Notifications
- From: Lanwench [MVP - Exchange]
- Re: Blocked UDP Traffic and New Message Notifications
- From: Lanwench [MVP - Exchange]
- Re: Blocked UDP Traffic and New Message Notifications
- Prev by Date: Re: Blocked UDP Traffic and New Message Notifications
- Next by Date: Re: ActiveSync 4.0 with Exchange 2003 SP2 (Problems setting up sma
- Previous by thread: Re: Blocked UDP Traffic and New Message Notifications
- Next by thread: Invalid Mailbox Exceeded Message
- Index(es):
Relevant Pages
|
