RE: Exchange 5.5 over WAN connection (new mail notifications)
Fix the routing. We route a mixture of RFC1918 and public addresses on our networks with no problems. And we've got a LOT of networks. -- Roger D. Seielstad - MCSE Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:31 PM To: Exchange Discussions Subject: Re: Exchange 5.5 over WAN connection (new mail notifications) Yes, I know it does not work on NATed addresses. I was just hoping some one had a easy fix. -John Q Jr. - Original Message - From: Morgan, Joshua [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 11:25 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Is the Internet address that they are being translated to a NAT address ? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -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] _ 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]
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]
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]
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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
You forgot to add the sarcasm tags. There are those that still require them. Tom. -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:08 PM To: Exchange Discussions 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
Check the archives. I believe we have discussed this about four times in the last month or so. Tom. -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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
I think you missed Andy's blazing sarcasm tag. I just assume it's always there unless someone else tells me he had a right answer. :) -Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:20 AM 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
-Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 17:20 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? He forgot the sarcasm tags. And also to add that the list's own elite squad of marines has been dispatched to the poster's work address to tattoo I *WILL ALWAYS* spend at least some time reading archives and maybe trying google, technet, asking around the office before posting. Especially given that the poster mentioned the beast that is causing his problem in the post itself. -- Robert Moir, MSMVP IT Systems Engineer, Luton Sixth Form College Rome did not create a mighty empire by having management meetings -- This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons or unauthorized employees of the intended organisations is strictly prohibited. The contents of this email do not necessarily represent the views or policies of Luton Sixth Form College, its employees or students. _ 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
Yeah, well.. just don't post the Koan link for him until Monday please, I still haven't transferred it from the old mail-resources.com website. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:08 AM To: Exchange Discussions 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
Have you changed jobs again? ;) -Original Message- From: Chris Scharff [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:27 PM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Yeah, well.. just don't post the Koan link for him until Monday please, I still haven't transferred it from the old mail-resources.com website. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:08 AM To: Exchange Discussions 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] -- 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
RE: Exchange 5.5 over WAN connection (new mail notifications)
That is a safe thing to assume when referring to Andy. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems -Original Message- From: Hunter, Lori [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:25 PM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) I think you missed Andy's blazing sarcasm tag. I just assume it's always there unless someone else tells me he had a right answer. :) -Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:20 AM 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] _ 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
Well, so far this morning I've been a sales engineer, technical writer, product tester, marketing rep and product manager. So I guess the answer to that question would be yes. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:41 AM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Have you changed jobs again? ;) -Original Message- From: Chris Scharff [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:27 PM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Yeah, well.. just don't post the Koan link for him until Monday please, I still haven't transferred it from the old mail-resources.com website. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:08 AM To: Exchange Discussions 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] -- 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
RE: Exchange 5.5 over WAN connection (new mail notifications)
Is the Internet address that they are being translated to a NAT address ? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -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] _ 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]
Re: Exchange 5.5 over WAN connection (new mail notifications)
ouch, ou, my a** is on fire from all the flames. I appreciate you all pointing out the obvious. But what I was looking for, YES I have read the archives, hence why I sent the issue in the post, is what's the fix? (i.e. I know the UDP packets are not being routed.) Now I will do some more research, as you have all pointed out the answer is probably out there! (X-files) But I just wanted to clarify why I posted, since, just as I missed Andy's sarcasm, some of you missed the point of my post. Thanks for making my day different, - John Q Jr. - Original Message - From: Chris Scharff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 10:46 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Well, so far this morning I've been a sales engineer, technical writer, product tester, marketing rep and product manager. So I guess the answer to that question would be yes. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:41 AM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Have you changed jobs again? ;) -Original Message- From: Chris Scharff [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:27 PM To: Exchange Discussions Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Yeah, well.. just don't post the Koan link for him until Monday please, I still haven't transferred it from the old mail-resources.com website. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:08 AM To: Exchange Discussions 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
Re: Exchange 5.5 over WAN connection (new mail notifications)
Yes, I know it does not work on NATed addresses. I was just hoping some one had a easy fix. -John Q Jr. - Original Message - From: Morgan, Joshua [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 11:25 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Is the Internet address that they are being translated to a NAT address ? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -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] _ 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]
RE: Exchange 5.5 over WAN connection (new mail notifications)
Are you in charge of your network config or do you have to go to another department? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:31 PM To: Exchange Discussions Subject: Re: Exchange 5.5 over WAN connection (new mail notifications) Yes, I know it does not work on NATed addresses. I was just hoping some one had a easy fix. -John Q Jr. - Original Message - From: Morgan, Joshua [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 11:25 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Is the Internet address that they are being translated to a NAT address ? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -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] _ 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]
Re: Exchange 5.5 over WAN connection (new mail notifications)
That's another guy! But I can get him do pretty much what ever I want! Why? - Original Message - From: Morgan, Joshua [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 12:25 PM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Are you in charge of your network config or do you have to go to another department? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -Original Message- From: John Q [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:31 PM To: Exchange Discussions Subject: Re: Exchange 5.5 over WAN connection (new mail notifications) Yes, I know it does not work on NATed addresses. I was just hoping some one had a easy fix. -John Q Jr. - Original Message - From: Morgan, Joshua [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, January 10, 2002 11:25 AM Subject: RE: Exchange 5.5 over WAN connection (new mail notifications) Is the Internet address that they are being translated to a NAT address ? PROFITLAB Network Engineer PH: (864) 250-1350 Ext 133 [EMAIL PROTECTED] -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] _ 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]
