[Pidgin] #1880: Windows Socket Error 10060

[Pidgin]

#1880: Windows Socket Error 10060
---------------------------+------------------------------------------------
  Reporter:  stonez        |       Owner:       
      Type:  defect        |      Status:  new  
  Priority:  minor         |   Milestone:       
 Component:  pidgin (gtk)  |     Version:  2.0.2
Resolution:                |    Keywords:       
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by stonez):

 Once again thank you for your response.  Something very odd here....I
 placed the PC into the DMZ and IT DID NOT fix the problem.  I then opened
 the windows firewall and added an exception there even though I wasn't
 using that firewall. Still no dice.  I then logged back into my router,
 and found an obscure setting which seems to have caused the issue.  The
 setting "all other protocols" needed to be checked, as shown in the
 screenshots.  This is on a 2Wire 2701HG-B Gateway.  In investigating a
 little further I tried creating a rule that allowed traffic on TCP 5190
 Outbound and Inbound but to no avail.  In looking at the AIM site, and the
 requirements for their traffic the only indicate that 5190 TCP is required
 but there must be something else traffic wise or in the router's "All
 Other Protocols" that prevents connecting.  I have an email into 2Wire to
 get more details on this setting.  Otherwise as long as I leave it
 selected (i.e. - Allow All Other Protocols) Pidgin works fine.  The odd
 thing is, that if I use the standard AIM Classic client even with All
 Other Protocols deselected in the router, that seems to work.  Could this
 maybe also point to something in Pidgin whereby extraneous traffic or some
 other port usage may be going on?  I will keep you apprised as I know
 more, and ask you do the same.  Thanks again for your time.

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