Windows socket error with pidgin when using AIM?
This worked for me,when I was experiencing Windows socket error #10060 errors. I dont know why it worked, but it did. The info came from a forum post in one of the tek tips style sites.
Open pidgin
Click on accounts near the top
Go to "Add/Edit"
Find your AIM account in here. Highlight it
Click Modify at the bottom of the Accounts window
In the modify account screen, click on the Advanced tab
Change the server to login.messaging.aol.com
Change the port to 80
Save your settings.
Apparently the default server entry is actually a DNS alias to login.messaging.aol.com, so rather than put that, I just entered login.messaging.aol.com directly. It may or may not work for you, please post if it does.
Update: Just changing the server name did not fix my problem. This thread on LinksysInfo.org (What's wrong with WRV200 now) gave me some tips that make me think the problem lies with my router. Dossy on #pidgin on irc.freenode.net also suggested changing the port to 80, which I have added to the instructions above.
7 Comments:
Hey, glad my suggestion worked for you. Indeed, changing the hostname shouldn't make any difference at all. It's all about what ports your router is allowing you to initiate outbound connections on. My guess is it blocks outbound 5190/tcp by default, but allows 80/tcp.
i had the same problem today and by changing the port to 80 as you described it worked!
thanks!
Yes! This fixed mine as well. Thanks!
I used the trick of setting to port 80 myself again yesterday, and worked like a champ. Much thanks again dossy.
I'm afraid, it didn't work as intended. Because, I could log in, but can't see any of my friends online in pidgin!
Wow, good job. That was very helpful, thanks. Anyone know the science behind this?
I have no idea why it works, i'm just thankful that it does. The frequent disconnections almost made me switch completely over to Google Talk, which would have left all my AIM friends unreachable.
Post a Comment
<< Home