Re: XP SP 2 changes Outlook 2000 behaviour...

From: run4yourlives (run4yourlives_at_gmail.com)
Date: 09/09/04


Date: 9 Sep 2004 08:07:18 -0700

Dude you need a new server... 60 seconds for email delivery is an eternity...

Ours is almost instantanous. Even with the av/spam filters.

"Star Fleet Admiral Q" <Star_Fleet_Admiral_Q(NOSPAM)@(SPAMNOT)hotmail.com> wrote in message news:<eDRSP7glEHA.1904@TK2MSFTNGP09.phx.gbl>...
> I doubt many corporate users would even notice a 60 second (that's 1 minute)
> delay - most corporate environment take longer than that for exchange to
> perform the necessary virus/worm/Trojan/malware/spammail scans (you are
> doing those on all mail - inbound/outbound internal/external - right),
> depending on what version of protection you are using.
>
> --
>
> Star Fleet Admiral Q @ your service
>
> *************************************************
>
> "run4yourlives" <run4yourlives@gmail.com> wrote in message
> news:df24d3fc.0409081428.233340d2@posting.google.com...
> > Just a message to all, since I had a hell of a time dealing with this
> > problem, and the "solutions" are few and far between; remaining
> > unacceptable in my mind.
> >
> > XP Service Pack 2 changes the way Outlook 2000 interacts with the
> > Exchange Server, causing a "delay" in sending and recieving mail.
> >
> > From MS:
> >
> > "The default preference for e-mail notification in Outlook is UDP, and
> > if that fails, then it uses polling...The default polling time is 60
> > seconds and is set at the Exchange Server."
> >
> > XP Service Pack 2 blocks all UDP communication between Outlook and
> > Exchange, EVEN IF THE FIREWALL IS "OFF"! (which makes me wonder what
> > "off" really means).
> > If someone can prove me wrong here, I'm listening, since all my
> > efforts to try and prove otherwise have failed.
> >
> > So, with SP2 on Windows XP, Outlook will run using RPC polling, which
> > defaults to a 60 second minimum value, meaning the maximum polling
> > time is 120 seconds. To a user this means email is delayed up to two
> > minutes.
> >
> > This is a noticable change for any user used to working with outlook
> > in a corporate enviornment; and to many unacceptable, as it pretty
> > much destroys the previous percieved real-time interaction. My gmail
> > account works faster.
> >
> > Furthermore, the 60 second polling interval is set by the Exchange
> > Server and requires the addition of a registry key on the server to
> > change. In addition, MS recommends that 60 seconds is the minimum
> > value used.
> >
> > Something for all those in corporate environments to be aware of.
> > Since we have a network firwall anyways, I'll be withholding
> > installing SP2 on corporate machines, lest I have to deal with people
> > thinking their outlook is broken.



Relevant Pages

  • Re: Troubleshooting that lousy "Requesting Data..." dialog box in OLXP
    ... This even happens when we're on the same network segment. ... Does increasing the timeout simply delay the box popping up or does it have ... Is there any reason why Outlook 98 did not have this issue? ... What about the server ...
    (microsoft.public.exchange.connectivity)
  • Re: Single user issue; best troubleshooting
    ... COULD be cause by that intermediate 'network access' server ... you do know there is significant logging in Outlook ... form of Integrated Authentication and so all of the OUTLOOK ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to allow POP3 SSL connections w ISA 2004
    ... the Outlook group as well. ... Firewall Client configuration for ISA Server 2004. ...
    (microsoft.public.windows.server.sbs)
  • RE: login and email problems
    ... To the Outlook issue, ... Run "ipconfig /registerdns" command to register the DNS server. ... Ensure that you have an Outlook profile configured for the server ... profile is not associated with a Microsoft Exchange Server e-mail account. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... We have already set up Outlook Web Access and purchase a SSL Certificate ... I have used the "outlook.exe /rpcdiag" to see if it uses the HTTP ... firewall through to the exchange server. ...
    (microsoft.public.windows.server.sbs)

Quantcast