If you are running the Sametime
This issue was first reported to Sametime Support on October 21, 2009. Sametime support established the root cause to be a recent change to Hostnames Google used for their incoming connection server IP’s (talkz.l.google.com). The following is one example of the change: Remote Host IP = 209.85.162.129″ HostName = el-out-f129.google.com”. was changed to Remote Host IP = 209.85.162.129″ HostName = el-out-f129.1e100.net”. This change broke the handshake sequence that Sametime Gateway follows to establish the XMPP connection and impacts all sametime gateway versions. A fix has been developed for Sametime Gateway Gateway version 8.0.2 and can be downloaded from Fix Central. Sametime Support strongly recommends upgrading to Sametime Gateway 8.0.2 HF3 before applying this fix.
You can download Hot Fix 3 for version 8.0.2 from Fix Central and there is a fix in test for 8.0.1. If you are on an earlier version of the gateway it looks like there is an upgrade in your future.
Thanks for the heads up Google. By that, I think Google gave practically no warning to IBM before it did that.
As a company we have stopped supporting chats with Google – the community had been disabled.
Too many IP address changes without warning and issues like you have reported. Stick with AOL and Yahoo as they do not change often if at all.