[Pidgin] #2839: Pidgin can't resolve AIM server DNS lookup
Pidgin
trac at pidgin.im
Tue Aug 28 18:11:25 EDT 2007
#2839: Pidgin can't resolve AIM server DNS lookup
--------------------------+-------------------------------------------------
Reporter: johnhab | Type: defect
Status: new | Priority: minor
Component: pidgin (gtk) | Version: 2.1.1
Keywords: | Pending: 0
--------------------------+-------------------------------------------------
I installed 2.1.1 a couple days ago and it was working fine (I connect to
MSIM, YIM, GWIM, GT and AIM), but now it can't connect to AIM. I try to
connect and I get "Could not connect to authentication server: Windows
socket error #10060". But the debug log says it can't do the DNSlookup for
login.oscar.aol.com. Even if I put in IPs for the Oscar servers
(152.163.241.120, .128, .24, .28 if correct from a list I found from a
websearch) in the AIM login config, I still get the 10060 error.
Is this AOL trying to shut AIM out to non-proprietary clients? Thx. John.
--
Ticket URL: <http://developer.pidgin.im/ticket/2839>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list