Home > Pidgin Error > Pidgin Error Resolving Scs.msg.yahoo.com

Pidgin Error Resolving Scs.msg.yahoo.com

Is yahoo really upgrading their servers? Here's what happens when a yahoo messenger connection gets dropped: (03:15:54) yahoo: 23 bytes to read, rxlen is 43 (03:15:54) yahoo: Yahoo Service: 0x54 Status: -1 (03:15:54) yahoo: 80 bytes to RichM says: June 24, 2009 at 10:04 am This used to work up until a couple days ago. You might try starting >>> Pidgin on the commandline with the '--debug' switch and see if that >>> spits >>> out anything useful. >>> >>> -Matt > > You can enable http://iipseconline.com/pidgin-error/pidgin-error-resolving-messenger-hotmail-com.html

But without the router in the mix, pidgin stays connected, even when idle. comment:7 Changed 9 years ago by a0z0ra ​http://developer.pidgin.im/ticket/496 comment:8 Changed 9 years ago by MarkDoliner Resolution set to duplicate Status changed from assigned to closed Note: See TracTickets for help on i am on suse 11.1 and using pidgin 2.5.6 I have uploaded a wireshark packet capture and here is the debug output Pidgin Debug Log : Thu 18 Jun 2009 08:30:26 Reply yadhie says: October 13, 2009 at 3:19 pm thanks for this posting..

Highlight each and press Modify to go through the info on the Proxy tab which needs to set to "Global Proxy Settings"..... Roger that. > > >>>> ...and it mentions AIM, but the context seems to suggest this has >>>> to do with >>>> setting up a service. > > Those are AIM-specific Sometimes after 10-20 minutes, this resolves itself. This has been a problem for the past 3 days for me also (yahoo im destroying connection) comment:19 follow-up: ↓ 29 Changed 8 years ago by deryni ronjie: Can you use something

Good to know my article help you guys. @delufix: thanks for pointing out my misstyped @cbstxbill : If I'm not mistaken, Yahoo changing their protocol (protocol 16?). nate says: July 2, 2009 at 8:26 am This is the latest fix, and it worked for me, to boot! comment:51 follow-up: ↓ 52 Changed 8 years ago by nerddtvg Just to update what I said earlier, I can not confirm what my problem was on my Fedora machine at work. Thank you!

The problem seems to be associated with the Yahoo server itself. I'll have to try to ping it when I'm having the problem. $ ping -i 60 scs.msg.yahoo.com PING scs.msg.yahoo.com (66.163.181.170) 56(84) bytes of data. 64 bytes from cs105.msg.mud.yahoo.com (66.163.181.170): icmp_seq=1 ttl=54 comment:76 Changed 7 years ago by nerddtvg I just tried out the new 2.5.7 release that was meant to fix this problem by implementing protocol version 16, and it worked for https://developer.pidgin.im/ticket/1415 If I type in ymail it does nothing.

What's the difference between the two bills? Why (to you) is FunPidgin (Carrier) worth using over Pidgin? -- I just placed a one dollar bill on my desk, and next to it I placed a hundred dollar bill. The /etc/hosts work-around described in bug 9386 solved it for me, so it seems to be a DNS issue of some sort. intstead, using 2.5.5 version with cn.scs.msg.yahoo.com make user can't join to any room…plz help..

Not reuploading. (14:42:55) dns: DNS query for 'scs.msg.yahoo.com' queued (14:42:55) account: Connecting to account (14:42:55) connection: Connecting. https://blog.mypapit.net/2009/06/solving-pidgin-yahoo-messenger-problem.html selection of type of proxy socks4/5/http and the username/password to access that proxy (Not any Yahoo/MSN/ICQ/Gmail validations..... What a great program when its working and yahoo doesn't make a workaround to stop it . Need to see how long does this last.

Given the behavior that we're seeing, and the HUGE influx of spam SMS coming out of the Yahoo network, I'd suggest that the servers that become unresponsive are not down, they're http://iipseconline.com/pidgin-error/pidgin-error-241.html A dump of my Debug window follows, minus my Yahoo username: (10:29:52) prefs: /purple/savedstatus/default changed, scheduling save. (10:29:52) account: Connecting to account ****@yahoo.com (10:29:52) connection: Connecting. Pidgin move to protocol 16, so it could support p2p file transfer and other fancy features in the new protocol. Cheers!!!

Reply Vikram says: August 2, 2009 at 10:32 am Thanks! Other >> options are: >> >> * No proxy >> * HTTP >> * Socks 4 >> * Socks 5 >> * Use Environmental Settings > > Those are Gnome-specific settings. There is no need for us to provide a way to specify multiple servers; instead there is a need for ISP's to fix their nameservers. check over here the same problem use to happen in my office and at my home.

However, I cannot seemed to find any old binaries on the web. Reply With Quote 09-15-2009,11:21 AM #4 Icarus View Profile View Forum Posts Visit Homepage Radioactive Wombat/Moderator Join Date Aug 2001 Location Somewhere, Texas Posts 9,628 Make sure whatever client you are Will all of our IM's be passing through the Great Firewall of China if we use that server?

which means that a standard http connection was successful through the proxy, the next step in yahoo's login process is username/pass verification over ssl which never happens.

When it *does* connect, it says that it is starting "keepalive" (whatever that means for yahoo - for msn hotmail it means a ping every 30 seconds). comment:61 in reply to: ↑ 60 Changed 7 years ago by nerddtvg Replying to pEEf: (version: 2.56 win32) This was happening to me a few months ago, then it cleared up on That would be IF the proxy requires validation, if not leave those spaces blank. account? >> >> Yes. > > Then you're only concerned with Yahoo-related settings, of which there > are few.

aimpauSeptember 3rd, 2008, 04:41 AMNo problem. I haven't done much downloading and installing outside of it, and have nearly always met with problems when I tried. easiest way would be to start a terminal(console) window, then type: pidgin -d >~/Documents/pidgin_debug.txt this will direct the information into a file you can open in a text editor (feel free this content But yum doesn't know it by either name. $ sudo yum --enablerepo=* info \*carrier\* | grep Name Name : openser-carrierroute $ sudo yum --enablerepo=* info \*pidgin\* | grep Name Name :

So it's OS related in a way, in that either the OS has a bug in how it deals with the dns cache, or pidgin is using the dns cache incorrectly. mofified account information. So it has something to do with windows and pidgin. indeed this was my last resort.

Also, on a seperate note: is there anyway to set pidgin to just notify when there's an increase in emails, and not when there's a DECREASE in emails. If I do get some extra time, I may just run some tests using the base code from libpurple to simulate what happens but I can't promise it. comment:26 Changed 8 years ago by darkrain42 Ticket #8983 has been marked as a duplicate of this ticket. As a side note, hitting Reconnect doesn't work for me as the addresses are cached and the first address returned on the list is going to be the same until that