You haven't been here long then. And you don't know Andy. The combination of the 2 can be lethal if you aren't careful. And that is also why you should check the archives before asking common questions like yours that get asked many times per week/month/day/whatever. But the quick answer to what you are looking for (because I am feeling nice today) is that you are probably blocking UDP on your firewall, or it could also be due to the fact that you are NAT'ing. New mail notifications are UDP packets.
Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems -----Original Message----- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:20 PM To: Exchange Discussions Subject: Re: Exchange 5.5 over WAN connection (new mail notifications) WOW! I have NEVER seen that statement made before on this list, that's scary. Is the sky still blue? -John Q Jr. ----- Original Message ----- From: "Andy David" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Thursday, January 10, 2002 10:07 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) I dont think anyone here has ever heard of this problem. -----Original Message----- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:04 PM To: Exchange Discussions Subject: Re: Exchange 5.5 over WAN connection (new mail notifications) I am having a serious problem with "new mail notifications" over a WAN. Basically they don't update until a user clicks on a nether message or waits in excess of 20 minutes. Needless to say users are frustrated by this due to the fact that they don't "think" their mail has been sent. Is there a work arround for this? Client side notification of disabeling "new mail notifications"? The description of why this particular situation does not work is below, read into if you wish. -John Q Jr. Currently machines on the WAN network are using internal IP addresses (which are not routable via our network). When the machines send packets to our network, the WAN router converts the IP addresses into a public IP address (an address our router can actually reply to). The problem in hand is that when Exchange receives packets from the client, it looks into the payload information (information inside the packet, not the header) to figure out where it should be sent. Case in point: Workstation 10.10.2.15 is connected to x.230.24156/57. Due to NAT, the Exchange servers sees x.154.10.42 connected (it can communicate back fine). Once the user receives a piece of mail, the Exchange server replies to 10.10.2.15 (it had to have looked this information up from the payload data) and of course this IP is not routable. _________________________________________________________________ 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] ---------------------------------------------------------------------------- -- The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis, Suhler & Associates, Inc. by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ============================================================================ == _________________________________________________________________ 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]
