Dear Calvin,
In Wawa's case, the properties of the NIC on the Exchange Server
needed to be modified. Let me describe with more detail.
From a mailbox on a different Exchange Server, I would send a test
message to the mailbox on the problem Exchange Server. Using Windows
Messaging on the problem Exchange Server, I could open the recipient mailbox
and see that the message was in the Inbox. However, at the Client PC,
Outlook did not show the new e-mail message in the Inbox. The NIC buffer on
the problem Exchange Server did not reach its limit, thus the New Mail
Notification was not sent to the Client PC. Before we modified the NIC
buffer, the Client PC would have to click on another Outlook folder for the
new message to "come down to" the Client PC.
I do not think that modifying the NIC properties on the Client side
will help you.
I vaguely remember reading other Tech Net articles that were close
to Wawa's situation, but not of help. They may help you. Perform a Tech
Net search on the following words.
UDP
MTU Size
New Mail Notification
Rob Garrish
Exchange Administrator
Wawa Inc.
610-558-8371
[EMAIL PROTECTED]
-----Original Message-----
From: Smith, Calvin C [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 20, 2001 12:42 PM
To: 'Exchange Discussions'; 'Garrish, Robert B.'
Subject: RE: Late delivery of mail
Your answer might do the trick. Was the NIC on the server or the
workstation. If it was on the server, I doubt that your answer is the one
because it is a high volume server.
-----Original Message-----
From: Garrish, Robert B. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 6:12 AM
To: Exchange Discussions
Subject: RE: Late delivery of mail
Dear Calvin,
I had a similar problem over a year ago.
The resolution here at Wawa was that my SA needed to adjust a
setting on the NIC. Some buffer in the NIC needed to reach a top limit,
before the NIC would interrupt the Processor, and thus return the New Mail
Notification message. There were very few mailboxes on this Exchange Server
at that time. Thus, not a lot of constant traffic.
Rob Garrish
Exchange Administrator
Wawa Inc.
610-558-8371
[EMAIL PROTECTED]
-----Original Message-----
From: Smith, Calvin C [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 10, 2001 07:06 PM
To: Exchange Discussions
Subject: RE: Late delivery of mail
Thank you for the suggestion of the FAQ. I looked up FAQ 3.24 as you
suggested and found this:
"The push notification of new mail uses a dynamically assigned port
in the range UDP 1024-UDP 65535. This is also controlled by the RPC
Portmapper service. There is no known way to fix this port.
The workstation and server are on the same network, (i.e. there is no
firewall between them). Usually there is no delay in the notice of new
mail, that is, the problem is intermittent. I have made another search of
the knowledge base pertaining to high ports and Exchange and find nothing
relating to delayed mail notification. Does anybody have any other leads
that I might follow?
-----Original Message-----
From: Daniel Chenault [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 06, 2001 9:52 AM
To: Exchange Discussions
Subject: Re: Late delivery of mail
FAQ on new mail notification
----- Original Message -----
From: "Smith, Calvin C" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Thursday, December 06, 2001 11:55 AM
Subject: Late delivery of mail
> What could cause Outlook to not see new mail until several hours after the
> recorded receipt data? All the messages arrived in the inbox close to the
> same time. Some messages came in through the Internet Mail Service and
some
> are internal to the Exchange site. All the messages show that the Sent
date
> and the Received date are within a few minutes of each other. The
Received
> date shows a time that is several hours before the message could be seen
in
> the inbox with Outlook 2000 SR-1 (9.0.0.3812. Server is running Exchange
> 5.5 SR4 on NT SR6a.
>
> The workstation running Outlook did not record any network outages.
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
