Marianne Case 20.Jun.02 04:43 PM a Web browser Sametime Connect 1.5; 2.5 Windows NT/2000
Greetings. We have a new Sametime 2.5 server but our connect clients are still using Sametime Connect 1.5.5. When I tested the interoperability between the new 2.5 Connect client and the old 1.5.5 client it worked fine in the test environment.
However, after setting up the production Sametime server, when someone using a 2.5 connect client starts a chat with a user logged on the 1.5.5 client it hangs the 1.5.5 user's Connect client.
I am assuming this has something to do with a problem encrypting the chat. If the 1.5.5 client initiates a chat with the 2.5 client it works fine.
The one setup instruction I skipped when I set up this system was that I used the same server document for the new 2.5 server as I had been using for the old 1.5.5 server. I basically set up the new server from scratch, using the same host name and IP address as the old. I figured that would be easier than performing all of the upgrade steps.
Now we have this weird problem. Has anyone had similar? I set up another test server and compared EVERY SINGLE field in the Sametime section of the server document, and made sure they are the same on my server as in test. Everything seems to match but I don't get this client hang in test, only production. Is there a hidden field or something that I can correct so that we can upgrade to the 2.5 client and have interoperability to users still using the 1.5.5 client?
Thanks for the consideration. If I don't hear anything here or from Lotus business partner support, my plan will be to take a weekend to delete the server and re-create everything from scratch.
Solarcom Holdings, Inc.