[Pidgin] #2485: Windows socket error #10060 in AIM Protocol

[Pidgin]

#2485: Windows socket error #10060 in AIM Protocol
---------------------------+------------------------------------------------
  Reporter:  Felbane       |       Owner:                                      
      Type:  defect        |      Status:  new                                 
  Priority:  minor         |   Milestone:                                      
 Component:  pidgin (gtk)  |     Version:  2.0.2                               
Resolution:                |    Keywords:  pidgin socket error 10060 bos server
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by Felbane):

 Replying to [comment:7 mollask]:
 > Replying to [ticket:2485 Felbane]:
 > > Hi,
 > >
 > > I have an intermittent issue with Pidgin versions 2.0, 2.0.1, and
 2.0.2, as well as GAIM, when attempting to log into the AIM Protocol.
 After about a minute of "connecting", I receive the following message:
 > >
 > > (Account Name) disconnected
 > > Could not connect to BOS server:
 > > Windows socket error #10060
 > >
 > > This error seems to be sporadic. AIM will occasionally connect only to
 disconnect with the socket error after a few minutes, hours, or days.
 > >
 > > I believe this issue is different than ticket number #1880 due to
 there being no firewall present. I apologize if I'm mistaken. I've
 disabled the router and Windows firewalls in attempts to find the source
 of the issue. The attached screenshot was taken directly after a seemingly
 random disconnect.
 >
 > See #2097 --  breaux found using login.messaging.aol.com works and so it
 did for me.


 Thanks very much for the reply, but as datallah said, we are having
 different issues. Changing the server name did not fix my problem. This
 also seems to be a problem with every version of Pidgin I've tried. I'm
 also encountering this issue on two different computers, on Windows XP and
 Ubuntu, and I've also found out that two friends of mine are having the
 same issue. One of them shares the same ISP, the other is a different
 cable ISP. I've been unable to connect for a couple of weeks now. AIM
 express seems to work fine, though.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2485#comment:8>
Pidgin <http://pidgin.im>
Pidgin