So what? You still own your domain. For instance, set up a DNS record pointing to the Exchange box as mail.company.innerhost.com and point their clients to it. That should do the trick quite nicely, IIRC.
------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] > Sent: Wednesday, October 30, 2002 11:42 AM > To: Exchange Discussions > Subject: RE: VPN breaks Outlook > > > They have their own ISPs. > > -----Original Message----- > From: Roger Seielstad [mailto:roger.seielstad@;inovis.com] > Sent: Wednesday, October 30, 2002 11:25 AM > To: Exchange Discussions > Subject: RE: VPN breaks Outlook > > > How are they getting to the Internet then? Publish a host in > your domain. > > ------------------------------------------------------ > Roger D. Seielstad - MCSE > Sr. Systems Administrator > Inovis - Formerly Harbinger and Extricity > Atlanta, GA > > > > -----Original Message----- > > From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] > > Sent: Wednesday, October 30, 2002 11:12 AM > > To: Exchange Discussions > > Subject: RE: VPN breaks Outlook > > > > > > OK, I agree, but some of them don't even have their own DNS. > > Then what? - the common denominator that would fit all > > customers is the HOSTS file. > > > > -----Original Message----- > > From: Chris Scharff [mailto:chris_scharff@;messageone.com] > > Sent: Wednesday, October 30, 2002 10:52 AM > > To: Exchange Discussions > > Subject: RE: VPN breaks Outlook > > > > > > I'd add the domain name to their DNS suffix search order. > > > > -- > > Chris Scharff > > EMS Sales Engineer > > MessageOne > > 512.652.4500 x-244 > > > > > -----Original Message----- > > > From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] > > > Sent: Wednesday, October 30, 2002 9: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? > > > > _________________________________________________________________ > > 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]
