Consider the following scenario:

•	You publish a Microsoft Exchange server for Outlook Web Access (OWA) in Microsoft Internet Security and Acceleration (ISA) Server 2006.
•	You configure a Web listener to use OWA Forms-based authentication.
•	You have a mobile device that runs the Symbian operating system.
•	You use this device to access the ISA Server computer that forwards the request to the OWA server.

In this scenario, the mobile device receives an incorrect logon form. This logon form may not be displayed correctly. Also, you cannot authenticate to the ISA server computer.

Back to the top

This problem occurs because ISA Server 2006 incorrectly identifies the User-Agent header that is sent by a Symbian-based browser as an unknown agent. ISA Server 2006 sends the default authentication form instead of the correct authentication form for the Symbian-based browser.

ISA Server 2006 incorrectly identifies the User-Agent header as an unknown agent because the ISA Server 2006 schema uses the name "Symbain" instead of "Symbian."

For more information about User-Agent header, visit the following Microsoft Web site:

Back to the top

To resolve this problem, download the Fix_symbian.js file from the ISAtools.org Web site. Then, run this file to change the spelling from "Symbain" to "Symbian" in the ISA Server 2006 schema. To download the Fix_symbian.js file, visit the following ISAtools Web site: To run the Fix_symbian.js file, follow these steps:

1.	Extract the Fix_symbian.js file from the compressesd (.zip) file and save it to a folder.
2.	At a command prompt, move to the folder where you saved the Fix_symbian.js file.
3.	Type cscript fix_symbian.js, and then pres ENTER.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.

Back to the top