problem with logging back in

Jan - Insurance Source jan at jmgcapitalventures.com
Wed Apr 11 16:24:45 EDT 2012


(16:23:11) util: Writing file prefs.xml to directory C:\Documents and
Settings\Recept\Application Data\.purple
(16:23:11) util: Writing file C:\Documents and Settings\Recept\Application
Data\.purple\prefs.xml
(16:23:27) account: Connecting to account jang at ana.pbx.dls.net/.
(16:23:27) connection: Connecting. gc = 0235B060
(16:23:27) dnssrv: querying SRV record for ana.pbx.dls.net:
_xmpp-client._tcp.ana.pbx.dls.net
(16:23:27) dnssrv: Couldn't look up SRV record. DNS name does not exist.
(9003).
(16:23:27) dnsquery: Performing DNS lookup for ana.pbx.dls.net
(16:23:27) dnsquery: IP resolved for ana.pbx.dls.net
(16:23:27) proxy: Attempting connection to 209.242.28.213
(16:23:27) proxy: Connecting to ana.pbx.dls.net:5222 with no proxy
(16:23:27) proxy: Connection in progress
(16:23:27) account: Connecting to account jang at ana.pbx.dls.net/.
(16:23:27) proxy: Connecting to ana.pbx.dls.net:5222.
(16:23:27) proxy: Connected to ana.pbx.dls.net:5222.
(16:23:27) jabber: Sending (jang at ana.pbx.dls.net): <?xml version='1.0' ?>
(16:23:27) jabber: Sending (jang at ana.pbx.dls.net): <stream:stream
to='ana.pbx.dls.net' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(16:23:27) jabber: Recv (190): <?xml version='1.0'
encoding='UTF-8'?><stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
from="localhost.dls.net" id="5b525224" xml:lang="en" version="1.0">
(16:23:27) jabber: Recv (265): <stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><m
echanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms></stre
am:features>
(16:23:27) jabber: Sending (jang at ana.pbx.dls.net): <starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(16:23:27) jabber: Recv (50): <proceed
xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
(16:23:28) nss: subject=CN=*.pbx.dls.net,OU=Domain Control
Validated,O=*.pbx.dls.net issuer=serialNumber=07969287,CN=Go Daddy Secure
Certification
Authority,OU=http://certificates.godaddy.com/repository,O="GoDaddy.com,
Inc.",L=Scottsdale,ST=Arizona,C=US
(16:23:28) nss: subject=serialNumber=07969287,CN=Go Daddy Secure
Certification
Authority,OU=http://certificates.godaddy.com/repository,O="GoDaddy.com,
Inc.",L=Scottsdale,ST=Arizona,C=US issuer=OU=Go Daddy Class 2 Certification
Authority,O="The Go Daddy Group, Inc.",C=US
(16:23:28) nss: subject=OU=Go Daddy Class 2 Certification Authority,O="The
Go Daddy Group, Inc.",C=US issuer=OU=Go Daddy Class 2 Certification
Authority,O="The Go Daddy Group, Inc.",C=US
(16:23:28) certificate/x509/tls_cached: Starting verify for ana.pbx.dls.net
(16:23:28) certificate/x509/tls_cached: Checking for cached cert...
(16:23:28) certificate/x509/tls_cached: ...Found cached cert
(16:23:28) nss/x509: Loading certificate from C:\Documents and
Settings\Recept\Application
Data\.purple\certificates\x509\tls_peers\ana.pbx.dls.net
(16:23:28) certificate/x509/tls_cached: Peer cert matched cached
(16:23:28) nss/x509: Exporting certificate to C:\Documents and
Settings\Recept\Application
Data\.purple\certificates\x509\tls_peers\ana.pbx.dls.net
(16:23:28) util: Writing file C:\Documents and Settings\Recept\Application
Data\.purple\certificates\x509\tls_peers\ana.pbx.dls.net
(16:23:28) certificate: Successfully verified certificate for
ana.pbx.dls.net
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <stream:stream
to='ana.pbx.dls.net' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(16:23:28) jabber: Recv (ssl)(525): <?xml version='1.0'
encoding='UTF-8'?><stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
from="localhost.dls.net" id="5b525224" xml:lang="en"
version="1.0"><stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><m
echanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compr
ession
xmlns="http://jabber.org/features/compress"><method>zlib</method></compressi
on><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features>
(16:23:28) sasl: Mechs found: DIGEST-MD5 PLAIN CRAM-MD5
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <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'/>
(16:23:28) jabber: Recv (ssl)(224): <challenge
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cmVhbG09ImxvY2FsaG9zdC5kbHMubmV0Iix
ub25jZT0iZmpodU1qY1ArNXNWd0JPMDl3RHZGTUthQmRweUZmNGU0UDI3eXVDUiIscW9wPSJhdXR
oIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge>
(16:23:28) sasl: DIGEST-MD5 client step 2
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <response
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9ImphbmciLHJlYWxtPSJsb2N
hbGhvc3QuZGxzLm5ldCIsbm9uY2U9ImZqaHVNamNQKzVzVndCTzA5d0R2Rk1LYUJkcHlGZjRlNFA
yN3l1Q1IiLGNub25jZT0iRHk5cUJFSlVOZzE1ZFVZc1BDOXNLRG9pZlNaZVNCbGhhekpBY1FOL1N
RWT0iLG5jPTAwMDAwMDAxLHFvcD1hdXRoLGRpZ2VzdC11cmk9InhtcHAvYW5hLnBieC5kbHMubmV
0IixyZXNwb25zZT02MzcxZDJhYzgzNGNkNTM4NDQ5YTQyZWQ5OGY3ZWMzMyxjaGFyc2V0PXV0Zi0
4</response>
(16:23:28) jabber: Recv (ssl)(77): <failure
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
(16:23:28) sasl: Mechs found: PLAIN CRAM-MD5
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <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>
(16:23:28) jabber: Recv (ssl)(77): <failure
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
(16:23:28) sasl: Mechs found: CRAM-MD5
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='CRAM-MD5'
xmlns:ga='http://www.google.com/talk/protocol/auth'
ga:client-uses-full-bind-result='true'/>
(16:23:28) jabber: Recv (ssl)(136): <challenge
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">PC0zOTc2Nzk2MDIzMTQ2MzI4NzYxLjEzMzQ
xNzU3OTk5ODBAbG9jYWxob3N0LmRscy5uZXQ+</challenge>
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): <response
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>amFuZyA5MGFhZDZkZjZhYjg0MmRiOWY1MzB
hZjI1OTRiODFjMg==</response>
(16:23:28) jabber: Recv (ssl)(16): </stream:stream>
(16:23:28) connection: Connection error on 0235B060 (reason: 0 description:
Server closed the connection)
(16:23:28) account: Disconnecting account jang at ana.pbx.dls.net/ (00E79330)
(16:23:28) connection: Disconnecting connection 0235B060
(16:23:28) jabber: Sending (ssl) (jang at ana.pbx.dls.net): </stream:stream>
(16:23:28) connection: Destroying connection 0235B060
(16:23:32) util: Writing file accounts.xml to directory C:\Documents and
Settings\Recept\Application Data\.purple
(16:23:32) util: Writing file C:\Documents and Settings\Recept\Application
Data\.purple\accounts.xml
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/x changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.
(16:23:36) prefs: /pidgin/blist/y changed, scheduling save.

Best regards,
~Jan

Jan Goldberg  
Licensed | Alliance & Associates 

Office: (407) 909-4774 | Office: (321) 251-5728 | Toll Free: (877) 909-4774
| Fax: (407) 386-3377 
Individual & Group Health Insurance | Life Insurance | Dental Plans  |
Accidental Plans  | Final Expense | Guaranteed Issue 
OFFICE HOURS:  MONDAY - THURSDAY 9AM - 9PM  |  FRIDAY 9AM - 5PM  |  SATURDAY
9AM – 4PM 

 

 

-----Original Message-----
From: David Woolley [mailto:forums at david-woolley.me.uk] 
Sent: Wednesday, April 11, 2012 4:08 PM
To: Jan - Insurance Source
Cc: support at pidgin.im
Subject: Re: problem with logging back in

Jan - Insurance Source wrote:
> 
> Thanks for your response.  It was for the Pidgin  Instant messaging, 
> everything was working fine and if I try to reconnect it says 
> disconnected - Server closed connection...
> 

Pidgin is not the server and the people who wrote and distribute Pidgin do
not operate an instant messaging server.

Let's try this another way:  open the debug window, attempt a connection,
cut and paste its contents into an email, but minimally obscure any
sensitive information (that includes any binary data printed out during an
authentication exchange).  That should allow us to work out what the server
is, and maybe suggest why it is going wrong.

-- 
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.



More information about the Support mailing list