Messages Not Appearing.

  • Thread starter midwestcabinetITDude
  • Start date
M

midwestcabinetITDude

I am the IT department for my company and we are having a problem that is
beyond my knowledge. In Outlook 2000 we are having problems seeing messages
that we recieve. If we are viewing the inbox and click on another folder then
several messages show up in the inbox. Its like they are there just hidden.
How do I fix this. Please help.
 
T

t_willi1

Hello,

I'm also in IT and have seen the same problem described here. The problem
began after SP2 was installed on our XP Pro systems. I have tried setting up
Outlook.exe as an 'Exception' to the new XP SP2 Firewall but this did not fix
the issue. I learned more about the issue here ->

http://support.microsoft.com/default.aspx?scid=kb;en-us;319572

I have verified that the Exchange server is not where the problem is and
routing UDP internally on our network is also not the problem. I also learned
that Outlook dynamically selects a UDP port between 1024-6XXXX to
communicate, but I cannot input such a wide range of ports as 'Exceptions' to
the SP2 Firewall because you can only add one port as an exception at a time
(would simply take too long and is not feasible to add them all).

I feel that I am not dealing with an isolated issue here and that there has
to be many others experiencing this because the setup here is very standard.
We have a Win2000 server running Exchange and all clients are XP PRO-SP2 with
Office XP / Outlook 2002. Every system here is fully updated with up to today
current patches / updates. The issue was not present prior to updating the
clients to SP2.

Any help with resolving this would be greatly appreciated!

Thanks!!!
 
T

t_willi1

Hello,

I'm also in IT and have seen the same problem described here. The problem
began after SP2 was installed on our XP Pro systems. I have tried setting up
Outlook.exe as an 'Exception' to the new XP SP2 Firewall but this did not fix
the issue. I learned more about the issue here ->

http://support.microsoft.com/default.aspx?scid=kb;en-us;319572

I have verified that the Exchange server is not where the problem is and
routing UDP internally on our network is also not the problem. I also learned
that Outlook dynamically selects a UDP port between 1024-6XXXX to
communicate, but I cannot input such a wide range of ports as 'Exceptions' to
the SP2 Firewall because you can only add one port as an exception at a time
(would simply take too long and is not feasible to add them all).

I feel that I am not dealing with an isolated issue here and that there has
to be many others experiencing this because the setup here is very standard.
We have a Win2000 server running Exchange and all clients are XP PRO-SP2 with
Office XP / Outlook 2002. Every system here is fully updated with up to today
current patches / updates. The issue was not present prior to updating the
clients to SP2.

Any help with resolving this would be greatly appreciated!

Thanks!!!
 
B

Brian Tillman

t_willi1 said:
I have verified that the Exchange server is not where the problem is
and routing UDP internally on our network is also not the problem. I
also learned that Outlook dynamically selects a UDP port between
1024-6XXXX to communicate, but I cannot input such a wide range of
ports as 'Exceptions' to the SP2 Firewall because you can only add
one port as an exception at a time (would simply take too long and is
not feasible to add them all).
Click to expand...

There's another message in this newsgroup or the m.p.outlook group that
describes how to fix the randomness of the UDP port.
 
M

midwestcabinetITDude

I found the fix to the problem. When we updated to SP2 for Windows XP we
started getting the problem. We figured out that the firewall was blocking
the messages from being delivered automatically. So if you turn off the
Windows Firewall your problem will cease to exist.

Midwestcabinet IT Dude
 
I

ITguy81

I work in my company's IT department and we recently began having this
problem as well. We are using Windows 2000 pro with Office 2000. Outlook
has been giving us this problem for maybe a month or two, and I've run out of
things to try. Since we're not using XP, does someone know how to fix this
issue for Win2K? Thanks.
 
Top