Your message dated Fri, 25 Jun 2010 10:49:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#541658: The solution!
has caused the Debian Bug report #541658,
regarding cannot open research.microsoft.com
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
541658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541658
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iceweasel
Version: 3.0.6-1
Iceweasel cannot open research.microsoft.com as well as many pages on the site.
For example, trying to open
http://research.microsoft.com/en-us/people/thoare/
results in a long interval with "Waiting for research.microsoft.com..." in the
status line and afterward in the message
Connection Interrupted
The connection to the server was reset while the page was loading.
The network link was interrupted while negotiating a connection. Please try
again.
[Try again]
Similar behaviour happens in konqueror. Epiphany opens the page without
problems.
The used system is lenny with libc6 version 2.7-18 and linux-image-2.6.26-2-686
version 2.6.26-18.
I hope you could fix the bug soon.
Thanks
Sasha.
------------------------------------------------------------
Stock Trading
Save big on Stock Trading Fees. Click Now!
http://tagline.excite.com/fc/FgElN1gva4H1WuhWPY1biRKmSIw1cL0H109TdDzt6WpTNNS56JtfVi3cHPy/
--- End Message ---
--- Begin Message ---
On Sun, Jun 20, 2010 at 04:10:59PM +0200, Daniel Gibson wrote:
> I finally found the solution:
>
> https://blue-labs.org/howto/mtu-mss.php
>
> i.e. your router needs to do mtu-clamping because microsoft seems to
> block all ICMP traffic (which is really defective).
> I thought my router did this but it turned out my iptables-command was
> incorrect.. the one from aforementioned website works.
The original reporter probably had some similar problem. Closing this
bug assuming this.
Cheers,
Mike
--- End Message ---
