The 85.25.140.85 server is online, operational, and responding (at least as of last night) ... unless you want data from the web server service on port 40916 (which we do). That just sits there and hangs. The traffic I was seeing was simply TCP handshake responses, and nothing else.xfluffee wrote:Now I'm really curious what kind of data was being received from that server. The size seems a little high for just an unreachable message.
Editing the hosts file on your local computer superceeds the "flushdns" and "BackgroundDownloader = 0" tricks that have been posted. You should go back to "BackgroundDownloader = 1" (which is the default) and you may need to do the flushdns one last time after adjusting your hosts file ... I don't know if Windows trusts its local cache before the hosts file or not. A reboot would accomplish the same thing.
You still could be stuck with your normal network latencies ("Please Wait", etc), but you can at least get past the background downloader. But when you choose one of the other IP addresses, choose randomly instead of just the first one listed ... try to spread the requests over both servers instead of loading up one
Incidentally, is it intentional that the background downloader client duplicates its transmissions to the server, including the transmission of packets out-of-order?
