Comment 5 for bug 95241

I just want to add that the same thing happens on firefox 2.0.0.3.

Curiously though, this problem only appears at my work place.

When using firefox on the same computer from a different network (home) everything works as expected.

What makes this bug so strange is that there is no firewall or proxy at work, which could interfere. Maybe there is some strange kernel tcp/ip & router interaction going on here, which is only triggered by gecko based browsers? Hard to imagine, but I am not an expert...