RE: How to replicate OST without VPN

  • From: "John Tolmachoff \(Lists\)" <johnlist@xxxxxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 18 Jun 2003 15:37:53 -0700

What is wrong with OWA?

John Tolmachoff MCSE CSSA
Engineer/Consultant
eServices For You
www.eservicesforyou.com

> -----Original Message-----
> From: Bill [mailto:portabillemail@xxxxxxxxxx]
> Sent: Wednesday, June 18, 2003 3:19 PM
> To: [ExchangeList]
> Subject: [exchangelist] How to replicate OST without VPN
> 
> http://www.MSExchange.org/
> 
> Hello,
> I can't find an answer anywhere.  We are a company of roving consultants
> and many NEVER come to the office.  Our problem is trying to get email
> when we are behind customer's firewalls.  Their firewalls won't allow VPN
> access out so the only thing left is OWA and PSTs with POP.  Both are bad.
> 
> I'm thinking that the only reliable way to accomodate this is some kind of
> HTTPS connection.  That might be some kind of HTTPS VPN, a special
> transport, or ???
> 
> Has anyone ever resolved this situation or have any thought?
> 
> We are on Exchange 2000.
> 
> TIA
> 
> Bill
> 
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> Leading Network Software Directory: http://www.serverfiles.com
> No.1 ISA Server Resource Site: http://www.isaserver.org
> Windows Security Resource Site: http://www.windowsecurity.com/
> Network Security Library: http://www.secinf.net/
> Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
> ------------------------------------------------------
> You are currently subscribed to this MSExchange.org Discussion List as:
> johnlist@xxxxxxxxxxxxxxxxxxx
> To unsubscribe send a blank email to leave-exchangelist-
> 1440469J@xxxxxxxxxxxxx



Other related posts: