That error is a known transient problem (worse on slower connections) with Internet Explorer version 5,6 and 7. Microsoft claims it is fixed in IE 8, http://support.microsoft.com/kb/927917/
It does not occur in any other browser, e.g. Firefox, Safari or Google Chrome.