I'm not discounting the fact that they want the collaborative features, I'm
merely saying that security "should" be a part of those features.  That's
just me though...

-----Original Message-----
From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] 
Sent: Wednesday, October 30, 2002 12:16 PM
To: Exchange Discussions
Subject: RE: VPN breaks Outlook


Our premise is that we allow all customers to use MAPI Outlook. No one wants
to only use OWA or POP3 or IMAP. They want all the (collaboration) features
of Exchange/Outlook as per Microsoft's promotional materials. If they only
needed to be able to send/receive mail, they would go with a simple and less
expensive POP3 provider.

-----Original Message-----
From: Ely, Don [mailto:dely@;TripathImaging.com]
Sent: Wednesday, October 30, 2002 11:44 AM
To: Exchange Discussions
Subject: RE: VPN breaks Outlook


But as an ASP wouldn't you just charge more for the services???  Maybe I'm
just being blind, but I would think one would want to provide a more secure
solution.  Of course, added costs go with that solution, but one would apply
those costs to their clients I would think...

-----Original Message-----
From: Chris Scharff [mailto:chris_scharff@;messageone.com] 
Sent: Wednesday, October 30, 2002 11:44 AM
To: Exchange Discussions
Subject: RE: VPN breaks Outlook


I can seee some instances where the support costs related to helping Windows
95 users install and configure VPN might make an ASP shudder. InnerHost is
certainly not the only ASP to provide Exchange access in that manner.

> -----Original Message-----
> From: Ely, Don [mailto:dely@;TripathImaging.com]
> Sent: Wednesday, October 30, 2002 10:14 AM
> To: Exchange Discussions
> Subject: RE: VPN breaks Outlook
> 
> 
> I would disagree with that...  A VPN solution with a  RADIUS server 
> would fit your needs quite well...
> 
> -----Original Message-----
> From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com]
> Sent: Wednesday, October 30, 2002 11:13 AM
> To: Exchange Discussions
> Subject: RE: VPN breaks Outlook
> 
> 
> MAPI across the Internet. Please no flames. There is no VPN that would 
> be universal enough for all kinds of customers.
> 
> -----Original Message-----
> From: Ely, Don [mailto:dely@;TripathImaging.com]
> Sent: Wednesday, October 30, 2002 10:28 AM
> To: Exchange Discussions
> Subject: RE: VPN breaks Outlook
> 
> 
> How do they connect?  VPN, Direct Dial??
> 
> Are these users POPing their email?
> 
> -----Original Message-----
> From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com]
> Sent: Wednesday, October 30, 2002 10:12 AM
> To: Exchange Discussions
> Subject: RE: VPN breaks Outlook
> 
> 
> Would you like me to give you an example?
> 
> we are a hosting company. Customers connect to our Exchange servers 
> from all over the world, from a variety of client OSes. Their machines 
> are not members of our domain. They can't possibly use our WINS.
> 
> What would you do to allow their PCs to resolve the short name of our 
> Exchange server?
> 
> 
> 
> -----Original Message-----
> From: Roger Seielstad [mailto:roger.seielstad@;inovis.com]
> Sent: Tuesday, October 29, 2002 4:31 PM
> To: Exchange Discussions
> Subject: RE: VPN breaks Outlook
> 
> 
> No there aren't. There are times in which its easier than doing it a 
> different way, but that doesn't mean there are times in which they 
> must be used.
> 
> ------------------------------------------------------
> Roger D. Seielstad - MCSE
> Sr. Systems Administrator
> Inovis - Formerly Harbinger and Extricity
> Atlanta, GA
> 
> 
> > -----Original Message-----
> > From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com]
> > Sent: Tuesday, October 29, 2002 2:17 PM
> > To: Exchange Discussions
> > Subject: RE: VPN breaks Outlook
> > 
> > 
> > there are some situations when one must use HOSTS file.
> > 
> > -----Original Message-----
> > From: Ely, Don [mailto:dely@;TripathImaging.com]
> > Sent: Tuesday, October 29, 2002 12:07 PM
> > To: Exchange Discussions
> > Subject: RE: VPN breaks Outlook
> > 
> > 
> > Neither, use WINS and DNS, works every time...
> > 
> > -----Original Message-----
> > From: RBHATIA [mailto:RBHATIA@;AIIM.ORG]
> > Sent: Tuesday, October 29, 2002 9:18 AM
> > To: Exchange Discussions
> > Subject: RE: VPN breaks Outlook
> > 
> > 
> > Is it the LMHOSTS file or the HOSTS file ?
> > 
> > -----Original Message-----
> > From: Tener, Richard [mailto:RTener@;midship.com]
> > Sent: Tuesday, October 29, 2002 9:24 AM
> > To: Exchange Discussions
> > Subject: RE: VPN breaks Outlook
> > 
> > 
> > yes you should use the lmhost file on the client pc to map to your
> > exchange server thats what we use here at my office and it
> works good.
> >  If you need
> > more help dont hesitate to email me.
> > 
> > rich
> > 
> > -----Original Message-----
> > From: JPC [mailto:jpciocon@;hotmail.com]
> > Sent: Monday, October 28, 2002 8:10 PM
> > To: Exchange Discussions
> > Subject: VPN breaks Outlook
> > 
> > 
> > Hi, folks:
> > 
> > Mixed mode, currently migrating users from 5.5 to E2k. Remote users
> > have Outlook 2002 on W2k Professional laptops and Alcatel 
> > PERMIT/Client.
> > 
> > These users connect via dial-up, they can access their
> mailboxes and
> > send/receive no problem.  When they use LinkSys router and
> DSL, they
> > can access our network, the internet and other network resources 
> > EXCEPT for their mailboxes on the E2k server.
> Synchronization failure
> > messages are
> > related to "network problems preventing access to the Exchange 
> > server" or the RPC message box "retrieving data from Exchange 
> > server".  These eventually fail and nothing is exchanged between the 
> > client and their server
> > mailbox.
> > 
> > Has anyone seen this?  If so, what tips would you suggest?
> > 
> > Thanks very much.
> > -Juancho
> > 
> > _________________________________________________________________
> > List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> > Archives:               http://www.swynk.com/sitesearch/search.asp
> > To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
> > 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:leave-exchange@;ls.swynk.com
> > 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:leave-exchange@;ls.swynk.com
> > 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:leave-exchange@;ls.swynk.com
> > 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:leave-exchange@;ls.swynk.com
> > 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:leave-exchange@;ls.swynk.com
> 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:leave-exchange@;ls.swynk.com
> 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:leave-exchange@;ls.swynk.com
> 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:leave-exchange@;ls.swynk.com
> 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:leave-exchange@;ls.swynk.com
> 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:leave-exchange@;ls.swynk.com
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:leave-exchange@;ls.swynk.com
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:leave-exchange@;ls.swynk.com
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:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to