I tried the workaround and logged the following: (15:47:28) util: Writing file prefs.xml to directory C:\Documents and Settings\HP_Administrator\Application Data\.purple (15:47:28) util: Writing file C:\Documents and Settings\HP_Administrator\Application Data\.purple\prefs.xml (15:47:30) account: Connecting to account [email protected]/qt. (15:47:30) connection: Connecting. gc = 0204D228 (15:47:30) dnsquery: Performing DNS lookup for typists.quicktate.com (15:47:30) dnsquery: IP resolved for typists.quicktate.com (15:47:30) proxy: Attempting connection to 75.126.220.109 (15:47:30) proxy: Connecting to typists.quicktate.com:5222 with no proxy (15:47:30) proxy: Connection in progress (15:47:30) proxy: Connecting to typists.quicktate.com:5222. (15:47:30) proxy: Connected to typists.quicktate.com:5222. (15:47:30) jabber: Sending: <?xml version='1.0' ?> (15:47:30) jabber: Sending: <stream:stream to='typists.quicktate.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> (15:47:30) jabber: Recv (392): <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1628149767' from='typists.quicktate.com' version='1.0' xml:lang='en'><stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><m echanism>PLAIN</mechanism></mechanisms></stream:features> (15:47:30) jabber: Sending: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (15:47:30) jabber: Recv (50): <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (15:47:30) nss: subject=CN=typists.quicktate.com,OU=Domain Control Validated - RapidSSL(R),OU=See www.rapidssl.com/cps (c)05,OU=GT04993935,O=typists.quicktate.com,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US (15:47:30) nss: subject=OU=Equifax Secure Certificate Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US (15:47:30) certificate/x509/tls_cached: Starting verify for typists.quicktate.com (15:47:30) certificate/x509/tls_cached: Checking for cached cert... (15:47:30) certificate/x509/tls_cached: ...Found cached cert (15:47:30) nss/x509: Loading certificate from C:\Documents and Settings\HP_Administrator\Application Data\.purple\certificates\x509\tls_peers\typists.quicktate.com (15:47:30) certificate/x509/tls_cached: Peer cert matched cached (15:47:30) certificate: Successfully verified certificate for typists.quicktate.com (15:47:30) jabber: XML parser error for JabberStream 0197FE50: Domain 1, code 5, level 3: Extra content at the end of the document (15:47:30) jabber: Sending (ssl): <stream:stream to='typists.quicktate.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> (15:47:31) jabber: Recv (ssl)(179): <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='3328678295' from='typists.quicktate.com' version='1.0' xml:lang='en'> (15:47:31) jabber: Recv (ssl)(162): <stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><m echanism>PLAIN</mechanism></mechanisms></stream:features> (15:47:31) sasl: Mechs found: DIGEST-MD5 PLAIN (15:47:31) jabber: Sending (ssl): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5' xmlns:ga='http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'/> (15:47:31) jabber: Recv (ssl)(148): <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>bm9uY2U9IjIxNzQxMzk5MjkiLHFvcD0iYXV 0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge> (15:47:31) sasl: DIGEST-MD5 client step 2 (15:47:31) jabber: Sending (ssl): <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9ImVjbGVjdGljIixyZWFsbT0 idHlwaXN0cy5xdWlja3RhdGUuY29tIixub25jZT0iMjE3NDEzOTkyOSIsY25vbmNlPSJQZ2haUUJ KNUVuTllKallKZTFjVGNHbEtHQlpvUEJOQVhUTWpTRmRnWER3PSIsbmM9MDAwMDAwMDEscW9wPWF 1dGgsZGlnZXN0LXVyaT0ieG1wcC90eXBpc3RzLnF1aWNrdGF0ZS5jb20iLHJlc3BvbnNlPTRiOTJ lMTIzMjk2NGZhZGQ1MmNmNmRmOTYwMjk4NzdiLGNoYXJzZXQ9dXRmLTg=</response> (15:47:31) jabber: Recv (ssl)(77): <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure> (15:47:31) sasl: Mechs found: PLAIN (15:47:31) jabber: Sending (ssl): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga='http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'>password removed</auth> (15:47:31) jabber: Recv (ssl)(71): <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><bad-auth/></failure> (15:47:31) connection: Connection error on 0204D228 (reason: 2 description: Authentication Failure) (15:47:31) account: Disconnecting account 00C94CC8 (15:47:31) connection: Disconnecting connection 0204D228 (15:47:31) jabber: Sending (ssl): </stream:stream> (15:47:31) jabber: XML parser error for JabberStream 0197FE50: Domain 1, code 5, level 3: Extra content at the end of the document (15:47:31) connection: Destroying connection 0204D228
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Atallah Sent: Wednesday, August 19, 2009 3:01 PM To: Sulabh Mahajan Cc: Laurie Shannon; [email protected] Subject: Re: FW: Problem connecting to the server On Wed, Aug 19, 2009 at 17:55, Sulabh Mahajan<[email protected]> wrote: > This appears to be a recently fixed bug #9956: > http://developer.pidgin.im/ticket/9956. > > (I am not sure, if someone can verify) > > You will have to wait for the release of 2.6.2 to be able to connect. I think the following workaround will allow you to connect: Enter the server name ("typists.quicktate.com") into the "Connect Server" field in the "Advanced" settings for your XMPP account. -D _______________________________________________ [email protected] mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
