Hi Hannes, Am 11.09.2014 um 20:48 schrieb Hannes Erven: > I remember a possibly similar situation back in 2008... the culprit was a > not-fully-up-to-date Cisco ASA firewall that corrupted TCP SACK fields and > hence had the remote site send RSET. > Anyways on our end the connection seemed to starve, just as you describe it. > > We detected that by comparing tcpdumps from both affected ends. Of course we > had been lucky enough to have that happen with a business partner with > competent IT people who we got a hold of, spotted the problem and also > temporarily switched the feature off on their side to prove that this > actually is the problem. > A firmware upgrade on my client's firewall then fixed the issue. > > With a server hosted somewhere and incoming connections from big clusters, > you might not be as lucky as that...
Yup. Looks like I'll just have to sit it out. This is just a small, private, low-traffic server, it's not like anyone at Amazon cares that I have problems. ;) And even if they did, I have neither the know-how nor the time and resources to do anything useful to fix it. I'll just keep my eyes open to see if it gets any worse and recommend my users have their Amazon and newsletter stuff sent to other Email addresses. The advantage of being small is that that really is a feasible option. :) Regards, Sean
