I'm afraid I know next to nothing about network troubleshooting. If you
be making the registry changes that Patrick pointed you to...
> No ISA, but a good old Proxy. The Proxy, however is not between the
> Server and the clients.
> Also, to add to this mystery, it has been working fine for more than 2
> months. Until something happened... but what?
> How can I verify and correct this UDP situation?
> > Your problem is likely to be somewhere in your network - some change has
> > probably started blocking the UDP packets. Do you run the ISA proxy
> > Some people who have encountered this problem have fixed it by
> > either the LDT (local domain table) or LAT (local address table) and
> > updating the ISA clients on the workstations.
> > --
> > Jeff Stephenson
> > Outlook Development
> > This posting is provided "AS IS" with no warranties, and confers no
> > > I can't believe that suddenly 65 clients would have the exact same
> > problem.
> > > I would suspect that the problem is on the server side.
> > > I don't know really in what direction I should go regarding your
> > suggestion
> > > to inspect the UDP thing.
> > > I re-applied Windows 2000 SP3 and Exchnge 2000 SP3, and of course...
> > > did not help!
> > > This is a very annoying problem.
> > > > This can happen when UDP packets (the mailbox refresh notifications)
> > from
> > > > the Exchange Server are not getting to the clients. You'll have to
> > > > your LAN traffic to figure out why UDP is no longer traversing
> > > > If you check out this article, you can apply some registry settings
> > > force
> > > > Outlook to poll the server using RPC rather than having it wait for
> > > > server to send it UDP packets.
> > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;305572
> > > > I believe the June 21st update for Outlook 2002 was the first to
> > > the
> > > > patched DLLs the article references.
> > > > --
> > > > PATRICK REED [Outlook - MVP]~~~~~~
> > > > -Microsoft Certified Professional (MCP)
> > > > -Have you checked http://www.slipstick.com?
> > > > > Hi,
> > > > > I have a problem with my Exchange 2000 Server.
> > > > > Messages don't display immediately in Outlook XP. Internal mails
> > > mails
> > > > > from outside.
> > > > > They will display in the Inbox only if you click on an other
> > > > > message (then you suddenly here the beep of an incoming message
> > > > > figure
> > > > > is displayed beside the Inbox).
> > > > > We do not use PST files, no OST or other things like that. Strange
> > > thing,
> > > > > even F9 or F5 won't help! You have to click on "another place" in
> > > Outlook
> > > > > to
> > > > > trigger the display of an incoming message.
> > > > > I first thought that Symantec Antivirus for Exchange 2000 3.0 was
> > > > > cause
> > > > > of this strange behavior, but I de-installed the antivirus
> > > > > (scary!), rebooted the server, even restarted the MTA on the
> > > 5.5
> > > > > that is still active on another machine, and still the problem
> > remained.
> > > > > I have no idea what causes this problem, but it is certainly a
> > > > > problem for most users, who, if they don't go and check manually,
> > > > > figure
> > > > > out only much later that there is some urgent mail in their Inbox!
> > > > > Message may display "by themselves" sometimes after 20-40 minutes.
> > > > > Any idea what can be wrong? The server is a US version of Exchange
> > 2000
> > > > > SP3
> > > > > on Windows 2000 Server SP3.
> > > > > Regards,
> > > > > Xavier Lescalier.