Below is the output that repeats itself in a loop. This is clearly an issue with my ISP, not a Pidgin bug. It occurs everyday at specific hours. I'm just trying to get a handle at what is wrong , because I acn't communicate with them at the "Pidgin level".
(18:15:25) *proxy:* Connecting to talk.google.com:5222 with no proxy (18:15:25) *proxy:* Connection in progress (18:15:31) *proxy:* Connecting to talk.google.com:5222. (18:15:31) *proxy:* Connected to talk.google.com:5222. (18:15:31) *jabber:* Sending ([email protected]/Home): <?xml version='1.0' ?> (18:15:31) *jabber:* Sending ([email protected]/Home): <stream:stream to=' gmail.com' xmlns='jabber:client' xmlns:stream=' http://etherx.jabber.org/streams' version='1.0'> (18:15:42) *jabber:* Recv (138): <stream:stream from="gmail.com" id="76279C9C7F14F024" version="1.0" xmlns:stream=" http://etherx.jabber.org/streams"; xmlns="jabber:client"> (18:15:45) *msn:* C: NS 000: PNG (18:15:46) *msn:* S: NS 000: QNG 49 (18:15:48) *jabber:* Recv (210): <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features> (18:15:48) *jabber:* Sending ([email protected]/Home): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (18:15:53) *jabber:* Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> (18:15:57) *nss:* Handshake failed (-5938) (18:15:57) *connection:* Connection error on 050BEC90 (reason: 5 description: SSL Handshake Failed) (18:15:57) *account:* Disconnecting account [email protected]/Home (023435D8) (18:15:57) *connection:* Disconnecting connection 050BEC90 (18:15:57) *connection:* Destroying connection 050BEC90 On Wed, Dec 16, 2009 at 1:06 AM, Paul Aurich <[email protected]> wrote: > And Moshe Cohen spoke on 12/15/2009 12:52 PM, saying: > > I have a problem with my ISP (does not happen when I connect via a > > different ISP) where Pidgin fails to connect to Google, but Google's own > > "Google Talk" Windows client is successful. > > > > What is the difference between the way the GoogleTalk Windows client > > connects to the way Pidgin (on Windows) behaves when connecting to > Google? > > The Google Talk client contains a number of fallbacks for different > situations, including using 'talk.google.com' (instead of relying on SRV > records. See [1] for details) and falling back to a connection on port 443 > if others don't work. > > Please attach the output of the Help->Debug Window from a connection > attempt, which should have enough information to indicate why Pidgin can't > connect. > > ~Paul > > [1] > > http://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#WhycantIlogontomyGoogleTalkGoogleAppsaccountanymore > >
_______________________________________________ [email protected] mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
