Re: 815052 - Windows XP-Based Clients Do Not Receive "New Mail" Notification Messages After You Install Service Pack 1

  • From: "Deus, Attonbitus" <Thor@xxxxxxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 06 Mar 2003 07:29:59 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 05:32 PM 3/5/2003, you wrote:

>The whole issue is very interesting. I have XP SP1 machines that
>don't seem to have this problem, even though XP SP1 is installed.

Same here.

>I have to ask "what is it about SP1 that alledgedly broke things and
>what does adding the domain to the LDT supposedly fix things?"

Exactly!

>If the UDP packet is from the Exchange Server on the same network,
>and if the XP firewall thing isn't enabled, when what's the problem?
>The Firewall client doesn't handle LAT based connections, and
>doesn't handle incoming connections, unless they're part of an
>ongoing session with the Firewall service. So, which is so special
>about these Exchange new mail modification messages? I suppose its
>time for a packet sniff -- but how the LDT enters into the mix is
>quite odd, since the LDT is just used for determining how a name
>should be resolved.

My thoughts as well... If the UDP packet is coming FROM the Exchange 
Server, what difference does it make if I have the FW client
installed on 
my box or not?  And in fact, it does not- I personally do not think
this 
has anything at all do to with the FW client or ISA, unless there is
some 
funky-ness going on when you have the FW installed WHEN you load XP
SP1.

I removed the FW client from my box, ensured I was not a SNAT client,
no 
proxy settings- basically made my system a regular-old network node
with no 
outside access, sat in Outlook on Send Items, telnetted into the
Exchange 
box on the same network, sent myself a message, and go no
notification- I 
had to click on Inbox to see it.  Again, this is without any FW
client or 
anything to do with ISA... Except for the fact that the Exchange
Server is 
a SNAT client.  But if that were the case, it would be that way for
ALL my 
XP clients with SP1, not just a few.  What is the likelyhood that
having 
the FW client installed when you apply SP1 has something to do with
it?  I 
guess I"ll have to test that...

t

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBPmdpeohsmyD15h5gEQJ1EACgh61vfIzDR3xTPRTcI9dWCM04bscAn2mA
dkqJxwX+YkjnZq6niW3mQ6PM
=CTBs
-----END PGP SIGNATURE-----



Other related posts: