Could you send this type of thing to the list server rather than to me directly?
I know the 55FE/2KBE works ok in a mixed 55/2000 environment but have no experience of it in a native E2K environment. A better alternative is to force the use of the "reach" OWA 2000 client. Either get your ISP users to use Netscape instead of IE5+ or use an ISAPI filter:- [this is from KC Lemson on the Exchange 2000 list server] #1: A filter that intercepts the User-Agent header on an inbound HTTP request, and sets it to a different value. Generally this is used to "force" the reach client even for IE5+. #2: A filter that intercepts all HTTP requests and re-directs the user to http://server/logon.asp. In the example I gave, this was used to implement forms/cookie-based authentication. The addition you could make is to have, on that logon.asp, a checkbox that says "Give me the reach client". Then if that option is checked by the user, the ASP would re-write the User-Agent header sent to the back-end to that of a reach browser. Creating ISAPI filters is easy as pie with VC6's ISAPI Extension Wizard. Here's a sample: 1. Start Visual C++, and choose "New" from the File menu. 2. Select "ISAPI Extension Wizard", give the project a name such as "UserAgent" and click OK 3. Check "Generate a Filter object" and uncheck "Generate a Server Extension object". Click Next. 4. Check "Post-preprocessing of the request headers" and click Finish. 5. This will create a new workspace in Visual C. The workspace will have one main file with the name of "CUserAgentFilter()". Doubleclick on this file in the workspace. 6. Scroll down to the "DWORD CCHeaderFilter::OnPreprocHeaders" function. 7. In this function, above the return value, insert the following text. The example below hardcodes the user-agent to that of Internet Explorer 4. char* sz; sz = "Mozilla 4.0 (compatible; MSIE 4.0; User-Agent Filter 1.0)"; pHeaderInfo->SetHeader(pCtxt->m_pFC, "User-Agent:", sz); 8. Under the "Build" menu, select "Build UserAgent.dll" or press F7 9. This will build a DLL for you, usually put in a location such as "C:\Program Files\Microsoft Visual Studio\MyProjects\UserAgent". Copy this DLL to your Exchange server. 10. On the IIS server, open Internet Services Manager 11. Right click on the virtual server for which you want to hard code the language and choose Properties. 12. On the "ISAPI Filters" tab, click Add and browse to your DLL. 13. Click OK and apply the changes 14. Restart IIS Admin service and W3SVC. Mark H -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 30 November 2001 06:11 To: [EMAIL PROTECTED] Subject: solution for running OWA5.5 as front end server Hi, I had read through the posting here & found out that we can actually set OWA5.5 as front end server with E2k as back-end server. I'm having some problem in the E2k server & OWA2k in my company. When some of the user do a dial up to ISP at home, they cant see anything in their inbox. I understand from microsoft website is actually cause by the WEBDAV protocol running on OWA2000. So, we are thinking of installing a OWA5.5 in a server which connect to our existing E2K server directly. May I know where can I get the step of doing this? Or maybe u have some documentation which can mail to me as a reference. Thanks. rgds, This e-mail, and any attachment, is confidential. If you have received it in error, please delete it from your system, do not use or disclose the information in any way, and notify me immediately. The contents of this message may contain personal views which are not the views of the BBC, unless specifically stated. _________________________________________________________________ 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]
