Hello everyone - I’m experiencing a problem with Domino Web Access and Sametime instant messaging. A few weeks ago we began using a fresh install of Lotus Domino Messaging Express 8.0.2. As you know, this version has some basic Sametime instant messaging functionality built-in. All of my users use Domino Web Access to access their email and calendars.
From the initial install up until a few days ago, my DWA users could go into their DWA preferences and enable Instant Messaging - upon doing so, they would be logged into Sametime upon logging into DWA. Users could send instant messages to each other. A few days ago, this functionality disappeared - enabling Instant Messaging is no longer an option in DWA Preferences and the presence box no longer appears after logging into DWA. However, anyone using the Notes client (presently only myself) can log into Sametime with no issues. Testing IM from the Domino Admin account on the server to my Notes login works fine, so I know that Sametime is working.
A reboot of the entire Domino server did not fix the issue.
My question is this - could someone point me into the right areas of my Domino configuration that need to be enabled so that Sametime works with DWA? I’m new to Lotus so I’m still feeling my way around the server - kinda lost with this one.
There are some DWA configuration settings you can set.
In your Notes Administrator, go to the Configuration tab, and select Server - Configurations. If you don’t have a configuration document for your server, create a new one. See the help if you need more info.
On the Domino Web Access tab of the config document take a look at the Instant Messaging section and see if you need to change any of the settings.
Our original problem was with a cluster document. But…
…we just upgraded for 8.0.1 to 8.0.2 (at IBM’s recommendation to resolve other issues) and now we have lost all web based access to Sametime (again)
A PMR is submitted to IBM, but I also submitted a PMR to address the fact that after the upgrade some features in the Notes Embedded ST client were lost.
They did call me back on the PMR, but his parting comment was “let me know if you find anything” and that was it.
We submitted another PMR, just as the Tech from the 1st PMR suggested and found that the upgrade had reset all of the tunneling (used for Web Access) to port that rendered them disabled.
We reset the port in the various places and restarted the server and everything worked normally.
Here’s what we looked at:
Title: How to enable or disable HTTP tunneling on a Sametime server over port 80