[Pidgin] #8853: Cannot connect to Yahoo - "connection refused" error

[Pidgin]

#8853: Cannot connect to Yahoo - "connection refused" error
--------------------------------------+-------------------------------------
 Reporter:  christophermerkel         |        Owner:  marv  
     Type:  defect                    |       Status:  new   
Milestone:                            |    Component:  Yahoo!
  Version:  2.5.5                     |   Resolution:        
 Keywords:  connection refused error  |  
--------------------------------------+-------------------------------------

Comment(by solarisjedi):

 This seems to be a yahoo server thing, and this happens to me occasionally
 with pidgin. Yahoo has many servers and they are round robin'ed in DNS. If
 you flush your dns cache in windows (ipconfig /flushdns) thus allowing
 your system to grab another IP of the many yahoo uses 9 out of 10 it will
 work for you again.

 Non-authoritative answer:
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.183
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.166
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.167
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.168
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.169
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.170
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.171
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.172
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.179
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.180
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.181
 Name:   scs.msg.yahoo.com
 Address: 66.163.181.182

 Mine was failing today on 66.163.181.166 with the exact same symptoms you
 described, so I flushed my dns cache and ping'ed scs.msg.yahoo.com again
 to grab a new IP from the list 66.163.181.182, afterward pidgin could
 connect once again. Your's may have started working again when your system
 naturally expired that DNS and grabbed a new IP (or that yahoo server
 started working again).

 It seems pidgin is letting the DNS round robin logic handle choosing the
 servers, which is fine. But yahoo's official client may cycle through them
 on it's own if one is not responding. (just a guess).

 Anyway, flushing your cache may help next time it happens to you.

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