I know my way around a computer pretty well, but this one has turned into a challenge that makes no sense to me. Connections to websites all work normally, except to Yahoo. Connecting directly to mail.yahoo.com brings me to the login screen normally, but when I log in and try to manage the inbox, that's where the problem starts. First, I will describe the symptoms, then a very long list of things I've done.
I can receive mail and I can open a message to read it. I can also compose a new message. But I can not send a new message, and messages received can not be deleted, forwarded, or moved to another folder, either from within the message or from the list of inbox contents. Instead, I just get a very long working state, and then a blank screen. This is not a Yahoo problem, not entirely anyway, since I can go to a different computer on the same home network and the problem does not happen. The symptoms are the same in 3 different Yahoo email accounts on different servers. Pings and tracerts to www.yahoo.com and mail.yahoo.com all look normal. This is the 'classic' Yahoo mail, not the new one - I switched to the new one in 1 of the 3 accounts, just long enough to verify that the problem was still there in the new version, then switched back to classic. I've kept a close eye on Google for other people having this kind of problem but seen almost nothing, so I guess it must be me, not Yahoo, though I was seriously suspecting some kind of conflicts with the new version they're pushing.
The network consists of the computer that does not have the problem, with a wireless connection to a Netgear router, and the computer that does have the problem connected via ethernet to the same router. The problem happens in Firefox 3.6, IE8, and Opera 11.
Since the problem began, I have replaced a large hosts file with the barebones one that only defines local host. I have verified that the lmhosts file is still the generic one. I have used the add/remove control panel to remove Java, restarted, used 2 different registry cleaners to eliminate any references to Java, then reloaded the latest Java and verifed the install at Java.com in Firefox and IE8. I have flushed the DNS and ARP caches (and of course the browser caches), reset TCP, verified that Ipsec is not running, and verified that TCP filtering is off. I have verified that Javascript is enabled. I have run a deep virus and spyware scan with AVG 11, then removed AVG to see if it was interfering. I have run a deep scan with Malwarebyte's Anti-Malware. I have also tried restarting with Zone Alarm Pro turned off. I have checked the router for any kind of settings that looked unusual. I have tried different ports on the router. I have disabled all ad- and script-blocking software. There's probably some other things that I just don't remember because it was 2:30am one of the nights this last week. Some of these things would be pretty unlikely to contribute to part of a web page working and part of it not working, but sometimes you just do something to get a clue that might spark an idea, right?
My gut says it's a Java problem, I can't think of anything else that would come into the picture after clicking a button in the Yahoo screen and that would be involved no matter which browser is used. I am seeing very long delays and lots of packet loss, so I could buy that the browser is just timing out on moving a message to a folder or deleting one or sending one, but I can't see how that fits with the other computer on the same network having no problem, unless the time-out is happening on my computer, not the connection, which brings me back to the xp networking components. Can't think of any way to test if it's a time-out issue with just certain actions. It's true that I've seen unusual delays in a ping to local host, where it takes a few seconds to display anything received, maybe even as much as 6-8 real-time seconds (!), but then it always says all 4 replies were received in less than 1ms. I don't know what to make of the long delay before seeing the replies in the command screen. Just for the record, the network stack consists of file/printer sharing unchecked, QoS checked (unchecked made no difference), and TCP. IP and DNS are obtained automatically. The router has a static IP.
Bottom line, it's not critical at all - everything else seems to work ok, and this was enough motivation to finally migrate away from Yahoo mail, so it's purely an intellectual challenge to figure out what's going on. If anybody else likes to tackle brain-teasers, I thought I'd share this one
Edited by mostlysane, 08 May 2011 - 02:53 PM.