[Pidgin] #1880: Windows Socket Error 10060

[Pidgin]

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

 In my case I found that opening a port range (both TCP and UDP) of 1024 -
 65535 in the gateway did not resolve the issue.  The reason I believe the
 AIM client works is because it uses HTTPS as the protocol, which as you
 can see in Shot3.jpg above, is enabled and allowed to pass through the
 firewall.  I also tried the option for having Pidgin listen in the range
 of 1024 - 65535 but would still get the socket error.  The only way I get
 Pidgin to work is to select the "All Other Protocols" checkbox.  Pidgin is
 using various TCP and UDP ports as shown using netstat -ab on a Win Vista
 or Win XP box.  When I do the same thing with AIM, it should HTTPS for the
 AIM.exe and since that (HTTPS) is allowed in my firewall/gateway, AIM
 works.  Couldn't Pidgin be setup to use SSL/HTTPS?  Is there any
 instructions for doing so???  Anyway just my $.02.

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