Many different error conditions can occur during the back-end server-to-server authentication process. Determine the causes of the different exception types, so you can address the issue.

When using Lotus Connections 2.5 with Windows Signle Sign-on, you must set additional WebSphere properties or you will receive the error 404 "File Not Found" when accessing certain URLs.

If Lotus Connections 2.5 is configured for Windows Single Sign-on and Blogs is configured for force authentication, users will get an access denied error message when they try to access the Blogs front page from a client machine within an Active Directory (AD) domain.

When Lotus Connections 2.5 is configured with Tivoli Access Manager, there are certain cases where WebSphere Application Server logs a NameNotFoundException error and Home page is not usable. This is caused by a configuration error.

If you set the browser locale to 'zh_hk' to access Lotus Connections, the user interface displays Simiplified Chinese, rather than Traditional Chinese.

The Ajax proxy can be configured to connect to another proxy before accessing the network. Connection to a pass-through proxy might be required if the Ajax proxy needs to go through a border firewall before accessing the network.

Anti-virus configuration settings in the IBM® Lotus® Connections information center do not accurately reflect the contents of the LotusConnections-config.xml file.

When editing a CSS file to be placed on an HTTP server in order to customize IBM® Lotus® Connections, it is important to delete all non-modified statements within the CSS file. To be clear, any statement in a modified class that is not modified should be removed. If you don't do this, all files referenced in a URL clause must be copied to the HTTP server. Also, the Information Center topic for dealing with edited lines that contain a file URL is incomplete.

When each IBM® Lotus® Connections application starts up it reads/validates all of the Lotus Connections configuration XML files, which are stored with the IBM® WebSphere® Application Server configuration files. An important point is that configuration in a file is NOT identified by the file name as one would expect - it is identified by the 'id=' attribute of the configuration element. Thus, if a Lotus Connections configuration file is saved by renaming it from LotusConnections-config.xml to LotusConnecti

The language selector link in the menu bar allows the user to select the IBM® Lotus® Connections language from the list specified in the LotusConnections-config.xml languageSelector element, thus overriding the browser language. The selected language is communicated throughout the Lotus Connections applications via what is called a browser cookie. Without a cookieDomain, the language cookie will only be used on the current server. If Lotus Connections applications are run on multiple servers with differ