That is what I see in my Notes status bar when I run my newly installed Notes 8.0.1 basic configuration client. It shows that I have successfully logged in to Sametime.

When I start Notes 8.0.1 (Eclipse), the story is a little different.

Same Sametime server. Same settings. Well, similar settings, given their redistribution and inconsistent nomenclature between the two UIs.

The Eclipse client is set to connect automatically, using SSO if available (it is). It is set to connect using the Sametime global connection setting, which is direct using Sametime protocol on port 1533. Keep alive is every 60 seconds.

And it doesn't work. At all *.

The basic configuration client is set to connect at Notes login, using SSO if available (it is). It is set to connect to the same Sametime server via a direct connection using Sametime protocol on port 1533. Keep alive is every 60 seconds.

And. It. Just. Works.


* It did partially work on 8.0, though SSO never worked.

Category: Notes 8
Technorati: IBM Lotus Notes+8 Sametime

1. Warren Elsmore05/03/2008 14:51:59
Homepage: http://www.elsmore.net

Is it the client type?
(http://lekkimworld.com/2008/03/03/notes_8_0_1_against_sametime_7_limited_use_server.html)

According to this technote there's only 1 client type for 801, but that assumed the technote is correct http://www-1.ibm.com/support/docview.wss?fdoc=wplcsame&rs=477&uid=swg21114318

I've not had any problems with 801 (apart from IBM's servers of course. THEY don't support the latest clients... )

2. Kevin Kanarski05/03/2008 15:06:59
Homepage: http://kkanarski.blogspot.com

I have the same issue with the 8.0.1 Standard Integrated ST client. I can't get Domino SSO to work. It works in the Notes 7 client and Notes 8 basic client. I have to enter my username and password in the 801 Standard client.

I can check the box for Use Domino SSO but when I go back to the preferences later it is unchecked.

3. Chris Linfoot05/03/2008 15:20:34

@1: Interesting theory and it may be that but...

sametime.ini on my ST server has no VPS_ALLOWED_LOGIN_TYPES= line at all.

And I used to be able to log in (not with SSO) with an 8.0 client.

I'll try that though and see if it makes any difference.

4. Bill Malchisky06/03/2008 07:15:55
Homepage: http://www.EffectiveSoftware.com

Have seen that with the ST 8.0.1 standard connect client on Windows going up against a ST7.x server. If they ST8 Linux client would actually setup correctly, I could try it there too...but that's for another day.

5. Stephen Farrell06/03/2008 17:14:39

Having the same issue,

Notes client is 8.0.1
Server is sametime 8
Domino server is 8.0.0

Client connects in basic mode but not in standard mode... if you find an answer please let me know. will do like wise.

Cheers,

Stephen

6. Terry06/03/2008 22:36:15

Having a similar issue -
Lotus Notes 8.0.1 (eclipse... or the slow version...)
Sametime 7.5.1 (server)

Using 8.0.1 client able to login to sametime fine withDomino SSO option (use Domino single sign on if available option).
However, I'm unable to make the client auto-login when I start Lotus Notes. I can make it auto-login as long as I don't use Domino SSO (the auto-login option is disabled for me when use Domino single sign on is selected).

FWIW - my username is entered as CN=Terry.../OU=X/O=Z and my sametime community is entered as a fully qualified host name (sametime.something.com) instead of SametimeServer/X/Z

7. Terry06/03/2008 22:52:20

@6 = me
Apparently I don't try hard enough.
I decided to log out of integrated sametime, go back into preferences and select -
1. remember password
2. automatically log in
3. use Domino single sign-on if available

Note that I tried this once and selected File - Sametime - Login to Sametime and was unable to login. I received the "temporarily unavailable" message mentioned above in the screenshot. I tried once more, but this time I closed Lotus Notes (exit the application completely) and re-launched the Lotus Notes client. This time I was automatically logged into sametime.

Good luck!

8. John12/03/2008 11:12:34

I finally got around this error by logging in with the full name (e.g. User Name/ORG) vice trying a shortname.

9. Kjeld16/04/2008 10:04:25

Hi,

I have just found this thread as I was working the ST SSO problem with Notes 801. I found that if you use SSO in Notes ST the canonicalized name is beeing used as login name.

I focused on the LTPA_UsrNm field in the Person Document and added the canonicalized name for the user. By doing this the canonicalized name will be added to the LPA token which seems to have solved the problem. I am not 100 % sure if this is the trick but till now it looks pretty good.

Regards,
Kjeld

10. Kjeld21/04/2008 07:53:01

Hi,

I just have to correct above. The change mentioned didnt do the trick. But by using the fully qualified host name when connecting I dont have the problem. ST logs in straight a head.

Kjeld

11. Michelle30/05/2008 15:46:18

In your server document, Internet settings to More Names,less security, you won't have touse the canonical name

Unable to post a comment? Please read this for a possible explanation...