Ovserved on today and yesterday'builds:2000-04-18-06-M15 and 2000-04-17-06-M15 comm builds. Steps to reproduce: Click QA on the Menu task bar, then Smoketests and #international links. Load the sites listed. Results: Alert warning message pop up saying " The connection was refused when attempting to connect at **** site." Then I have to start from a new application in order to continue. This won't happen until I loaded two or three sites randomly. I am not sure it is only my own machine problem or not. So I post it up for vote.

This only happens on M15 Win 32 builds. I didn't see this behavior on M16 Win 32.

I found out this is not international bug. It seems that http://www.tvspielfilm.de page destroys the DNS. After you go to the site, the warning error will show up any URL you go to. Steps of reproduce 1. Go to http://www.apple.com/ -no problem 2. Go to http://www.tvspielfilm.de/ -warning error "The connection was refused...° will display. 3. Go to any URLs -warning error will display This happens in 2000041806 M15 Win32 build under Win98. This does not happen in same build under Winnt 4.0. However, this does not happen in 2000041809 M16 Win32 build under Win98. That means this happens only in M15 build not M16 build.

Gordon should investigate this.

I am able to reproduce this with M15 on Win 98. I am using proxies. Once one URL is refused, all are refused. If I open Navigator 4.08 at the same time (without closing M15) and try to access the same URL, I often get: Connection refused (TCP error: not enough memory) Navigator 4.08 seems to only gives this error for URLs listed in the proxy exclusion list. My proxy exclusion lists for M15 and Navigator 4.08 are identical. Once I quit M15, Navigator 4.08 performs correctly.

This bug also occurs when not using proxies. My usual way of getting this to reoccur is to open the following: http://www.altavista.com/ http://www.tvguide.com/listings/ You may try to enter a zip code and submit that form. It always breaks. I get this error within about 30 seconds of trying to browse ANYTHING... it makes the browser unusable, blows up my TCP/IP stack and thus damages other programs. I think the priority of this bug should be greatly increased because it makes the current build unusable.

Is this related to bug 31125?

This bug is pretty old, and appears to be fixed.

Verified as fixed in 10-01 build.