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 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]

Reply via email to