While at LoLA this week I got stuck with a Sametime Meeting problem, R8.0.2 server.
The issue was one would login to a Sametime Meeting, but after about a minute, the screen would automatically refresh. And keep doing it every 75 seconds or so.
We had just moved the physical server so my first guess was an incorrect IP address someplace was causing it. Indeed I found one reference which had not been changed to the new IP(Q/A teams at IBM I feel your pain).
Didn't change it.
Looked at the Firewall, added some ports (different firewall was in use at the other location)and got closer but something was still wrong.
Checking the java console showed the connection trying to connect to the correct name, but incorrect IP, used the internal one while an external person would try to connect. DNS is fine, but there it was.
Open the stconfig.nsf database and went through the options and found an IP address instead of the FQHN (Fully Qualified Host Name).
Under Meeting Services, find:
HTTP Tunneling Host Name: server.company.com
Under CommunityConnectivity:
Community Trusted IPS: internal#,external#
Changed those references and restarted the server and now it stays up and connected.
Goes to show that even when you test something works, you need to test it under different circumstances to make sure it works as designed.
Speaker, Blogger, Author. Posts about HCL Digital Solutions, HCL Software, Lotus, Management, Collaboration, Competitive Intelligence and Strategy, Productivity, CRM and B2B Marketing.
I feel the pain - I often run into issues where the DNS names are not available at the beginning of a project and once available sometimes the clean-up process overlooks (or downright forgets) to correct all IP entries . . . . c
ReplyDeleteThat sounds like what happened almost exactly. We had to change IP twice unexpectedly.
ReplyDelete