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.
Wednesday, October 6, 2010
Friday, September 17, 2010
Got Doc neighborhood errors for office 2010?
Domino Document Manager or as I call it Domino.doc or DomDoc is no longer keeping up to date, in fact it is end of life already.
For those of you with the ODMA connector installed and upgrading to Office 2007 or 2010 and get an error message when trying to save something, in this case it was Visio for me, the only MS Office product I use, you would get an error saying you can not use the doc neighborhood.
Since we still support DomDoc clients and I did not want to break what works on my laptop, there is an IBM Technote #1230216, called "Change ODMA integration using the Windows registry" that outlines how to selectively turn off ODMA in specific applications.
It worked very well and I want to make sure everyone who needs it can use it as a number of Doc customers come out of the woodwork and you may find yourself wondering what is wrong.
For those of you with the ODMA connector installed and upgrading to Office 2007 or 2010 and get an error message when trying to save something, in this case it was Visio for me, the only MS Office product I use, you would get an error saying you can not use the doc neighborhood.
Since we still support DomDoc clients and I did not want to break what works on my laptop, there is an IBM Technote #1230216, called "Change ODMA integration using the Windows registry" that outlines how to selectively turn off ODMA in specific applications.
It worked very well and I want to make sure everyone who needs it can use it as a number of Doc customers come out of the woodwork and you may find yourself wondering what is wrong.
Subscribe to:
Posts (Atom)