If it's any help, we'v had this problem with a number of ISPs. It looks like some run caches that only accept a limited set of HTTP verbs, and throw away any request that uses others. This nobbles OWA. We found the answer was to put a certificate on the server and get people to access it via https:. Web proxies/caches have to tunnel SSL traffic, and we've had no further problems.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Andrea Coppini > Sent: Wednesday, October 02, 2002 3:14 AM > To: Exchange Discussions > Subject: RE: OWA from a client behind FW > > > Thanks for the Q, but these servers (or the clients) are not behind a > proxy. > > Apparently it's an ISP issue. A colleague of mine tried it from his > home Cable connection (which is on the same ISP as the office) and he > had the same problems. I tried it using my home ADSL connection > (different ISP) and it was fine. > > Spooky... > _________________________________________________________________ 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]
