Win XP sp2 + Outlook XP - no new email notification (exch 2003 - FIREWALL OFF)

[RJ]

Testing Windows XP sp2

Firewall in "domian" disabled via GPO - and confirmed that it is not
enabled on any network interfaces. So - firewall should be "off".

Exchange server is 2003/2003 - and is unchanged/untouched.

Office is Office XP sp2 and is untouched.

All clients except WinXPsp2 clients get instant email notification,
sp2 clients do not. Clearly, UDP packets from Exchange are not making
it to the client to notify of new email. Clicking a folder/email will
force connection and everything works. (eMails get "stuck" in outbox
too)

This is exactly the same behaviour as if the firewall was turned on
(same in sp1) - and is exepcted, but with firewall turned off???

Looking at other posts, I see many with a similar problem and none
with a real answer. I have tried setting Outlook as a general
exception to no avail.

Sorry for the x-post but it does fit into multiple groups, and other
"similar" messages are in each group - and sometimes referred to the
others.

TIA!

 

[Charley Munger]

We had the same problem, if we send an e-mail, it would show in bold in the
OUTBOX, and even though it's in bold, which gives the thought it is stuck and
not getting sent, it was sent. If you were to click on ANY folder in
Outlook the bold in the OUTBOX would go away.
Also, if your outbox was still in bold, you will not receive any incoming
mail until you clear that bold.
Adding Outlook.exe to the exception list fixed that for us.

 

[Bert Köhler]

Hi Ryan,
We are experiencing the same problem. Currently, I am trying to confirm this
by upgrading another PC from Win XP SP1 to Win XP SP2. The rest of the
environment will stay untouched.

The reply from Charley does not quite match the problem description. With
firewall switched off, firewall settings for Outlook should have no effect.

Bert.

 

[Bert Köhler]

P.S.:
Are you using third party sync software, e.g. Palm Hotsync or similar?

Bert.

 

[RJ]

I can't see any other replies apart from yours....

I am directly aware of at least one other company (not linked) who
have exactly the same issue - and their firewall is also off.

We are using BlackBerry desktop which syncs with email, but this is a
server-side sync and NOT client-side. So I am confident (and can
prove) this is not related.

I have also read other cases - but no responses annoyingly.....

If I find an anwer I will post here, but still stuck at the moment....

 

[Bert Köhler]

Hi RJ,
I will try to find out tomorrow if the Exchange server even sends a UDP
packet after all. (Sniffer on server)

Reinstalling/Repairing Office XP did not quite solve the problem. Seems as
if Outlook reacts 3-20 seconds too late. I will check that again. Might be
some other failure.

Bert.

P.S.: Where do you live? I just want to know your local timezone because
then I know when to expect replies...

Bert.
City: Hamburg
Country: Germany
Continent: Europe
Planet: Earth

;-)

 

[Bert Köhler]

Hi RJ,

Testing...

Interim result:
It is not the case that the client computer does not receive the UDP packet.
In fact, the Exchange server does not send the UDP packet. So, I assume that
the registration for the 'new email notification' failed with WinXPSP2, and
Outlook falls back to polling every one or two minutes.

Using the 'Repair Office' option did _not_ help.

Bert.

 

[RJ]

We agree with a 5-30 second delay with the firewall service enabled.

We're in UK - but google takes 6-12 hours to update newsgroups....
I'll try and email you direct...

 

[Bert Köhler]

Hi Ryan, and all other readers that might have the same problem:

I think I've got the solution (It works for our german installation)
The server does not even send UDP packets, as I suspected. But that is not
the server's fault; the client does not register for the 'new email
notification'. It does so because of the 'ForcePolling'-parameter which was
introduced with Office SP1 to have a workaround when the network environment
uses NAT, which in turn lead to not delivering the UDP packets.
If you now do it just the other way round and set this parameter to 0, it
did not initially work. I created the second registry key and set it to 0.

First Key+Value (Setting to 0 did not help; OL re-sets it to 1 every time it
starts):
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\RPC\ForcePolling

Second Key+Value (Setting this to 0 did help!):
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\RPC\ForcePolling
The only issue is: a normal user cannot create nor set the value, but you
should be able to work around this.

I found the description by googling for: ForcePolling rpc sp2

This is the link:
http://office.meetholland.com/message/105586.aspx, and it even worked for
our combination with OL2002. Normally, you do not have to add OUTLOOK.EXE as
an exception.
Stopping and starting the firewall service had no effect on my (german)
desktop PC, but it had an effect on a colleague's machine (english
installation). He deactivated the firewall for all the LAN connections
(Advanced tab).

Bert.