Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#13120 closed defect (fixed)

####@gmail.com/ disconnected "Unable to connect"

Reported by: MysteriousMrE Owned by: rekkanoryo
Milestone: Component: unclassified
Version: 2.7.8 Keywords: Connection problems gmail
Cc:

Description (last modified by rekkanoryo)

I continue to get an error which claims only 'Unable to connect' whenever I attempt to login to my gmail account from Pidgin. I'm using the newest version, I am not behind a firewall. Debug mode produces the following information.

(15:58:48) util: Writing file prefs.xml to directory C:\Users\Mr. E\AppData\Roaming\.purple
(15:58:48) util: Writing file C:\Users\Mr. E\AppData\Roaming\.purple\prefs.xml
(15:58:55) account: Connecting to account eric.g.backman@gmail.com/.
(15:58:55) connection: Connecting. gc = 0588F4F0
(15:58:55) dnssrv: querying SRV record for gmail.com: _xmpp-client._tcp.gmail.com
(15:58:55) dnssrv: Couldn't look up SRV record. No records found for given DNS query. (9501).
(15:58:55) dnsquery: Performing DNS lookup for gmail.com
(15:58:55) dnsquery: IP resolved for gmail.com
(15:58:55) proxy: Attempting connection to 72.14.204.17
(15:58:55) proxy: Connecting to gmail.com:5222 with no proxy
(15:58:55) proxy: Connection in progress
(15:59:01) util: Writing file accounts.xml to directory C:\Users\Mr. E\AppData\Roaming\.purple
(15:59:01) util: Writing file C:\Users\Mr. E\AppData\Roaming\.purple\accounts.xml
(15:59:16) proxy: Connecting to gmail.com:5222.
(15:59:16) proxy: Error connecting to gmail.com:5222 (Connection timed out.).
(15:59:16) proxy: Connection attempt failed: Connection timed out.
(15:59:16) jabber: Couldn't connect directly to gmail.com.  Trying to find alternative connection methods, like BOSH.
(15:59:16) dnssrv: querying TXT record for gmail.com: _xmppconnect.gmail.com
(15:59:16) dnssrv: Couldn't look up TXT record. DNS name does not exist. (9003).
(15:59:16) jabber: Unable to find alternative XMPP connection methods after failing to connect directly.
(15:59:16) connection: Connection error on 0588F4F0 (reason: 0 description: Unable to connect)
(15:59:16) account: Disconnecting account eric.g.backman@gmail.com/ (01430E78)

Change History (4)

comment:1 follow-up: Changed 8 years ago by rekkanoryo

  • Description modified (diff)
  • Status changed from new to pending

This page has relevant information. The overall point is your DNS server is busted. You can try using talk.google.com as the value for the Connect Server field on the account's advanced tab.

comment:2 in reply to: ↑ 1 Changed 8 years ago by MysteriousMrE

  • Status changed from pending to new

Replying to rekkanoryo:

This page has relevant information. The overall point is your DNS server is busted. You can try using talk.google.com as the value for the Connect Server field on the account's advanced tab.

If my DNS is broken, why isn't it having an effect on anything else? I don't know enough to claim you're wrong, but that sounds rather broad, considering absolutely nothing else on my computer has a problem, and I can connect to the gchat client just fine.

comment:3 Changed 8 years ago by MysteriousMrE

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 8 years ago by rekkanoryo

For the XMPP prptocol (which Google Talk uses), Pidgin relies on a special type of DNS record called SRV (short for "service"). Not all DNS servers support this record, and some that claim to support it don't handle it correctly. Home broadband "routers" are particularly notorious for this particular form of brokenness. (Home routers generally act as a DNS server to allow computers on the "internal" network to reference each other by DNS names. Some of them even cache resolved records so that additional requests for the same record don't hit the ISP DNS server again--this saves a tiny amount of bandwidth).

The official client works for Google Talk because it has a hard-coded fallback to talk.google.com, which we have not done.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!